CVE-2025-38310

seg6: Fix validation of nexthop addresses

MEDIUM

5.5

CVSS Score

Published: July 10, 2025 at 07:42 AM UTC

Updated: June 17, 2026 at 09:16 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: seg6: Fix validation of nexthop addresses The kernel currently validates that the length of the provided nexthop address does not exceed the specified length. This can lead to the kernel reading uninitialized memory if user space provided a shorter length than the specified one. Fix by validating that the provided length exactly matches the specified one.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

11.0

Linux Kernel · Linux

95%

4.14 ≤ v < 5.15.1864.14 ≤ v < 6.1.1424.14 ≤ v < 6.12.344.14 ≤ v < 6.15.34.14 ≤ v < 6.164.14 ≤ v < 6.6.945.16 ≤ v < 6.1.1426.13 ≤ v < 6.15.36.2 ≤ v < 6.6.946.7 ≤ v < 6.12.344.14d1df6fd8a1d22d37cffa0075ab8ad423ce656777

Vendor states this is fixed in 668923c474608dd9ebce0fbcc41bd8a27aa73dd6 (fixed)

Vendor states this is fixed in 7632fedb266d93ed0ed9f487133e6c6314a9b2d1 (fixed)

Vendor states this is fixed in cd4cd09810211fa23609c5c1018352e9e1cd8e5a (fixed)

Vendor states this is fixed in cef33a86bcb04ecf4dc10c56f6c42ee9d1c54bac (fixed)

Vendor states this is fixed in d2507aeea45b3c5aa24d5daae0cf3db76895c0b7 (fixed)

Vendor states this is fixed in d5d9fd13bc19a3f9f2a951c5b6e934d84205789e (fixed)

Vendor states this is fixed in 4.14 (unaffected)

Vendor states this is fixed in 5.15.186 (unaffected)

Vendor states this is fixed in 6.1.142 (unaffected)

Vendor states this is fixed in 6.12.34 (unaffected)

Vendor states this is fixed in 6.15.3 (unaffected)

Vendor states this is fixed in 6.16 (unaffected)