CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 1eadcb43893b897ade85ac5bf5c618054bc3c655, 472aba2603ca74c4f7722cb0c0296942b0776b8d, 7097a0280b178237265681be66d1bef11d15894b; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1eadcb43893b897ade85ac5bf5c618054bc3c655, 472aba2603ca74c4f7722cb0c0296942b0776b8d, 7097a0280b178237265681be66d1bef11d15894b; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ila: reload IPv6 header after pskb_may_pull in checksum adjust ila_csum_adjust_transport() caches ip6h = ipv6_hdr(skb) before calling pskb_may_pull(). On a non-linear skb whose transport header sits in a page fragment, pskb_may_pull() can call __pskb_pull_tail() / pskb_expand_head() and free the old skb head, leaving ip6h dangling; the following get_csum_diff(ip6h, p) then reads freed memory. ila_update_ipv6_locator() uses ip6h (and the iaddr derived from it) again after the csum-adjust call and additionally writes the new locator through that pointer. Impact: a remote IPv6 packet routed through a configured ILA csum-adjust-transport route or receive-side mapping triggers a slab-use-after-free in ila_update_ipv6_locator() (KASAN). The route or mapping requires CAP_NET_ADMIN to configure, but trigger packets are unauthenticated once it exists. Reload ip6h after each pskb_may_pull() in ila_csum_adjust_transport() before the csum-diff read. In ila_update_ipv6_locator() only the ILA_CSUM_ADJUST_TRANSPORT case pulls the skb, so reload ip6h and iaddr in that case alone before the destination-address write; the neutral-map modes never pull and keep their cached pointers.
- Published
- Aug 10, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-416
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
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
- 4.5affected
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before e451a904606c571f731ef7a06b3398619dce5300affected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before 1eadcb43893b897ade85ac5bf5c618054bc3c655affected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before ba353caafb06ccee57b78d3254e3cebf1dea4a93affected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before 896a9512d0d83c2a4b357e5585b7b62a8e3f95c1affected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before 7097a0280b178237265681be66d1bef11d15894baffected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before 472aba2603ca74c4f7722cb0c0296942b0776b8daffected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0cccaffected · git
- 33f11d16142b06588eedfc1dd8cf93790979a712 and later · before 92d3817649df2b0b6a008a686c8275c88d7ef594affected · git
- before 4.5not 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 | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.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
Published before and after this one in the same product
- ← EarlierCVE-2026-68123Aug 10, 2026 · openvswitch: fix GSO userspace truncation underflow39Monitor
- ← EarlierCVE-2026-68125Aug 10, 2026 · mac802154: llsec: reject frames shorter than the authentication tag35Monitor
- Later →CVE-2026-68128Aug 10, 2026 · ice: reject out-of-range ptype in ice_parser_profile_init35Monitor
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 | 1eadcb43893b897ade85ac5bf5c618054bc3c655 | Vendor (CNA) |
| Linux Linux | 472aba2603ca74c4f7722cb0c0296942b0776b8d | Vendor (CNA) |
| Linux Linux | 7097a0280b178237265681be66d1bef11d15894b | Vendor (CNA) |
| Linux Linux | 896a9512d0d83c2a4b357e5585b7b62a8e3f95c1 | Vendor (CNA) |
| Linux Linux | 92d3817649df2b0b6a008a686c8275c88d7ef594 | Vendor (CNA) |
| Linux Linux | ba353caafb06ccee57b78d3254e3cebf1dea4a93 | Vendor (CNA) |
| Linux Linux | c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc | Vendor (CNA) |
| Linux Linux | e451a904606c571f731ef7a06b3398619dce5300 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | 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).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()39Monitor
- CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()39Monitor
- CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update39Monitor
- CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification39Monitor
- CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
- CVE-2026-720835 days apartscsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE39Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
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)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/472aba2603ca74c4f7722cb0c0296942b0776b8d
- git.kernel.org/stable/c/7097a0280b178237265681be66d1bef11d15894b
- git.kernel.org/stable/c/896a9512d0d83c2a4b357e5585b7b62a8e3f95c1
- git.kernel.org/stable/c/92d3817649df2b0b6a008a686c8275c88d7ef594
- git.kernel.org/stable/c/ba353caafb06ccee57b78d3254e3cebf1dea4a93
- git.kernel.org/stable/c/c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc
- git.kernel.org/stable/c/e451a904606c571f731ef7a06b3398619dce5300
Vendor advisories and official records. Exploit/PoC links are deliberately left out.