xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full
In the Linux kernel, the following vulnerability has been resolved: xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full The depth check in xfrm6_input_addr() is off by one: if (1 + sp->len == XFRM_MAX_DEPTH) goto drop; ... sp->xvec[sp->len++] = x; xfrm_input() can leave sp->len == XFRM_MAX_DEPTH, and the transport-mode receive path re-enters IPv6 input via xfrm_trans_reinject() with that secpath preserved. If the inner packet carries a destination-options HAO option or a type-2 routing header, xfrm6_input_addr() is called with sp->len == XFRM_MAX_DEPTH; the check (1 + 6 == 6) is false, so sp->xvec[sp->len++] writes one slot past the 6-element xvec[]. The write stays within the sec_path allocation (invisible to KASAN); UBSAN_BOUNDS flags it and panics under panic_on_warn. Use "sp->len >= XFRM_MAX_DEPTH", matching xfrm_input(). This also restores one chain level the old check rejected at sp->len == 5. UBSAN: array-index-out-of-bounds in net/ipv6/xfrm6_input.c:309:10 index 6 is out of range for type 'xfrm_state *[6]'
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.8% · 53th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.25affected
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 91fc387f63c00ddfb5221127a17bac97549a8343affected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 68e8737fe8e72f085c608cff322b3d2de8340af1affected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 8fe2c53fb81f5ad5be43af2ad09583f7c78b4b77affected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before bdcda866c89f9a8b1acdabf02d26cde9fbe501d8affected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 48996649222e95008cdb98cd58579e3fc8e5ee06affected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 0f679e0523ddfff3fb554336ceb874b0e51e9cd3affected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 5f35a29a5eed3d80befd32050843ac88dea3d61aaffected · git
- 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and later · before 5d9e3bf34fec9a5d237e4b7cef4a707bc2e091bcaffected · git
- before 2.6.25not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | all versions | — |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f679e0523ddfff3fb554336ceb874b0e51e9cd3 | Vendor (CNA) |
| Linux Linux | 48996649222e95008cdb98cd58579e3fc8e5ee06 | Vendor (CNA) |
| Linux Linux | 5d9e3bf34fec9a5d237e4b7cef4a707bc2e091bc | Vendor (CNA) |
| Linux Linux | 5f35a29a5eed3d80befd32050843ac88dea3d61a | Vendor (CNA) |
| Linux Linux | 68e8737fe8e72f085c608cff322b3d2de8340af1 | Vendor (CNA) |
| Linux Linux | 8fe2c53fb81f5ad5be43af2ad09583f7c78b4b77 | Vendor (CNA) |
| Linux Linux | 91fc387f63c00ddfb5221127a17bac97549a8343 | Vendor (CNA) |
| Linux Linux | bdcda866c89f9a8b1acdabf02d26cde9fbe501d8 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0f679e0523ddfff3fb554336ceb874b0e51e9cd3
- git.kernel.org/stable/c/48996649222e95008cdb98cd58579e3fc8e5ee06
- git.kernel.org/stable/c/5d9e3bf34fec9a5d237e4b7cef4a707bc2e091bc
- git.kernel.org/stable/c/5f35a29a5eed3d80befd32050843ac88dea3d61a
- git.kernel.org/stable/c/68e8737fe8e72f085c608cff322b3d2de8340af1
- git.kernel.org/stable/c/8fe2c53fb81f5ad5be43af2ad09583f7c78b4b77
- git.kernel.org/stable/c/91fc387f63c00ddfb5221127a17bac97549a8343
- git.kernel.org/stable/c/bdcda866c89f9a8b1acdabf02d26cde9fbe501d8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.