CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg()
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.50% (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 0d8a12d7143126afdf9fbe2e3d438650dd6603ed, 35e0297a93c3c34a3924eeef816c03504e3ab5c5, 50ff092633b06382e5091dd5b093ce943d4ac2f9.
Low priority for now. Upgrade to Linux Linux 0d8a12d7143126afdf9fbe2e3d438650dd6603ed, 35e0297a93c3c34a3924eeef816c03504e3ab5c5, 50ff092633b06382e5091dd5b093ce943d4ac2f9 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: tipc: fix UAF in tipc_l2_send_msg() Syzbot reported a slab-use-after-free in ipvlan_hard_header() when called from tipc_l2_send_msg(). The root cause is that tipc_disable_l2_media() calls synchronize_net() while b->media_ptr is still valid. This allows concurrent RCU readers to obtain the device pointer after synchronize_net() has finished. The pointer is cleared later in bearer_disable(), but without any subsequent synchronization, allowing the device to be freed while still in use by readers. Fix this by clearing b->media_ptr in tipc_disable_l2_media() before calling synchronize_net(). This is safe to do now because the call order in bearer_disable() was reversed in 0d051bf93c06 ("tipc: make bearer packet filtering generic") to call tipc_node_delete_links() (which needs the pointer) before disable_media(). https: //lore.kernel.org/netdev/6a2c1007.428ffe26.258b27.015d.GAE@google.com/T/#u
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- —
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.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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.4affected
- 282b3a056225b35024246f63feb91d769d714dad and later · before 609ced2301be1df7e7ed2ef47d1d916674e6ba3baffected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before 71aafa16d79b107b33837f60b6cbc7d0cb8c5708affected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before f4002f1c669cc02e3763f479fc25ff1dfa9e2420affected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before 50ff092633b06382e5091dd5b093ce943d4ac2f9affected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before aef12b5ce793dea6b3a97a58fd0f946000ae8945affected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before 0d8a12d7143126afdf9fbe2e3d438650dd6603edaffected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before 35e0297a93c3c34a3924eeef816c03504e3ab5c5affected · git
- 282b3a056225b35024246f63feb91d769d714dad and later · before f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6affected · git
- before 4.4not 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-72501Aug 15, 2026 · RDMA/bnxt_re: Initialize dpi variable to zero0Monitor
- ← EarlierCVE-2026-72502Aug 15, 2026 · tcp: ipv6: clamp default adverting MSS to avoid GSO_BY_FRAGS (0xFFFF)30Monitor
- Later →CVE-2026-74256Aug 15, 2026 · bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check33Monitor
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 | 0d8a12d7143126afdf9fbe2e3d438650dd6603ed | Vendor (CNA) |
| Linux Linux | 35e0297a93c3c34a3924eeef816c03504e3ab5c5 | Vendor (CNA) |
| Linux Linux | 50ff092633b06382e5091dd5b093ce943d4ac2f9 | Vendor (CNA) |
| Linux Linux | 609ced2301be1df7e7ed2ef47d1d916674e6ba3b | Vendor (CNA) |
| Linux Linux | 71aafa16d79b107b33837f60b6cbc7d0cb8c5708 | Vendor (CNA) |
| Linux Linux | aef12b5ce793dea6b3a97a58fd0f946000ae8945 | Vendor (CNA) |
| Linux Linux | f4002f1c669cc02e3763f479fc25ff1dfa9e2420 | Vendor (CNA) |
| Linux Linux | f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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).
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
- 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/35e0297a93c3c34a3924eeef816c03504e3ab5c5
- git.kernel.org/stable/c/50ff092633b06382e5091dd5b093ce943d4ac2f9
- git.kernel.org/stable/c/609ced2301be1df7e7ed2ef47d1d916674e6ba3b
- git.kernel.org/stable/c/71aafa16d79b107b33837f60b6cbc7d0cb8c5708
- git.kernel.org/stable/c/aef12b5ce793dea6b3a97a58fd0f946000ae8945
- git.kernel.org/stable/c/f4002f1c669cc02e3763f479fc25ff1dfa9e2420
- git.kernel.org/stable/c/f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.