CVE-2026-74609: tipc: read le->link under the node lock in tipc_node_link_down()
Noroxi assessment
Priority: Monitor (action score 31/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2be741ad565c610871a6a95062c12c39da7168fd, 47ba70891b10b2feb52462086b7fcd2ad75d3ce3, 5558a8312452ddb21eff22b1cbd84302ad951944; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2be741ad565c610871a6a95062c12c39da7168fd, 47ba70891b10b2feb52462086b7fcd2ad75d3ce3, 5558a8312452ddb21eff22b1cbd84302ad951944; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.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: tipc: read le->link under the node lock in tipc_node_link_down() tipc_node_link_down() caches the link pointer before taking n->lock: struct tipc_link *l = le->link; /* unlocked */ if (!l) return; tipc_node_write_lock(n); if (!tipc_link_is_establishing(l)) { /* deref l */ ... tipc_link_reset(l); /* write into l */ if (delete) { kfree(l); le->link = NULL; The delete=true caller frees that very object under n->lock, so the lock does not protect the cached pointer against it: - CPU A, delete=false: tipc_rcv() on TIPC_LINK_DOWN_EVT, or the link supervision timer via tipc_node_timeout(), reads l unlocked and then dereferences it under n->lock; - CPU B, delete=true: netlink TIPC_NL_BEARER_DISABLE -> bearer_disable() -> tipc_node_delete_links() -> tipc_node_link_down(n, bearer_id, true) -> kfree(l). The link is freed with plain kfree(), not kfree_rcu(), and for UDP bearers disable_media() only schedules the asynchronous cleanup_bearer() work, so its synchronize_net() runs after the links are already gone. An in-flight CPU A that has read l therefore dereferences freed memory once B frees it: a use-after-free read in tipc_link_is_establishing(), and a use-after-free write via tipc_link_reset() on the establishing branch. The following trace was captured on 7.2.0-rc5-00284-gaf39eb111ce6: BUG: KASAN: slab-use-after-free in tipc_link_is_establishing (net/tipc/link.c:285) Read of size 4 at addr ffff88802e2aa068 by task swapper/2/0 tipc_link_is_establishing (net/tipc/link.c:285) tipc_node_link_down (net/tipc/node.c:1076) tipc_node_timeout (net/tipc/node.c:843) Allocated by task 9549: tipc_link_create (net/tipc/link.c:490) tipc_node_check_dest (net/tipc/node.c:1279) tipc_disc_rcv (net/tipc/discover.c:252) tipc_udp_recv (net/tipc/udp_media.c:389) Freed by task 9549: tipc_node_link_down (net/tipc/node.c:1084) tipc_node_delete_links (net/tipc/node.c:1320) bearer_disable (net/tipc/bearer.c:414) __tipc_nl_bearer_disable (net/tipc/bearer.c:992) Move the le->link read inside tipc_node_write_lock(), so it is serialised against the kfree() in the delete path. A racing teardown now either has not run yet, and we see a valid link, or has already run, and we see NULL.
- Published
- Aug 22, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.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
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before 2be741ad565c610871a6a95062c12c39da7168fdaffected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before 69d209461c110388710e483a130caf051e4fd09aaffected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before de017c22135f545ca4e65d1eada22887b64958ebaffected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before 47ba70891b10b2feb52462086b7fcd2ad75d3ce3affected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before a714d62513befef37f71f4ae89bb1fe173b65f2eaffected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before c3f2347a47754eac690967cfd82cb6d559817b07affected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before 5558a8312452ddb21eff22b1cbd84302ad951944affected · git
- 73f646cec35477b5099d7e952297cb9e1855be45 and later · before cba9ccb47e9fa4cc77692fb896cc5ab57a667882affected · 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-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-74607Aug 22, 2026 · KVM: SVM: Serialize accesses to the owner and mirror list with separate lock35Monitor
- ← EarlierCVE-2026-74608Aug 22, 2026 · smb: client: Fix use-after-free in cifs_try_adding_channels()39Monitor
- Later →CVE-2026-74610Aug 22, 2026 · tls: don't leave a full plaintext sk_msg ring unpushed31Monitor
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 | 2be741ad565c610871a6a95062c12c39da7168fd | Vendor (CNA) |
| Linux Linux | 47ba70891b10b2feb52462086b7fcd2ad75d3ce3 | Vendor (CNA) |
| Linux Linux | 5558a8312452ddb21eff22b1cbd84302ad951944 | Vendor (CNA) |
| Linux Linux | 69d209461c110388710e483a130caf051e4fd09a | Vendor (CNA) |
| Linux Linux | a714d62513befef37f71f4ae89bb1fe173b65f2e | Vendor (CNA) |
| Linux Linux | c3f2347a47754eac690967cfd82cb6d559817b07 | Vendor (CNA) |
| Linux Linux | cba9ccb47e9fa4cc77692fb896cc5ab57a667882 | Vendor (CNA) |
| Linux Linux | de017c22135f545ca4e65d1eada22887b64958eb | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-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).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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/47ba70891b10b2feb52462086b7fcd2ad75d3ce3
- git.kernel.org/stable/c/5558a8312452ddb21eff22b1cbd84302ad951944
- git.kernel.org/stable/c/69d209461c110388710e483a130caf051e4fd09a
- git.kernel.org/stable/c/a714d62513befef37f71f4ae89bb1fe173b65f2e
- git.kernel.org/stable/c/c3f2347a47754eac690967cfd82cb6d559817b07
- git.kernel.org/stable/c/cba9ccb47e9fa4cc77692fb896cc5ab57a667882
- git.kernel.org/stable/c/de017c22135f545ca4e65d1eada22887b64958eb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.