CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev
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 0e243671bc7b8eaf00f83dd2f4367436dc0cff98, 145812b678de9f3b59780173be3c0d22ed60dd93, 14e812ab41df0cac033479da835ec9a5de633404; 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 0e243671bc7b8eaf00f83dd2f4367436dc0cff98, 145812b678de9f3b59780173be3c0d22ed60dd93, 14e812ab41df0cac033479da835ec9a5de633404; 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: ipv6: prevent in6_dev_get() from resurrecting inet6_dev in6_dev_get() reads dev->ip6_ptr under RCU and then unconditionally increments its refcount. Device teardown can clear the pointer and drop the last reference between these operations. The increment then resurrects an object whose RCU free has already been queued, so callers can use it after it is freed. Use refcount_inc_not_zero() and return NULL when the object has already reached zero. RCU keeps the memory accessible through the attempted reference acquisition, and a successful increment pins the object for the caller. An independent run on the exact unpatched 6f5156d7a31a (v7.2-rc3) kernel reproduced the invalid reference acquisition as UID 1000: refcount_t: addition on 0; use-after-free. ip6_mc_source+0xef4/0x17e0 It was followed by the corresponding reference underflow in ip6_mc_source(). The supplied trace from the same unpatched revision additionally shows the access after the RCU read-side section ends: BUG: KASAN: slab-use-after-free in mutex_lock+0x76/0xe0 Write of size 8 at addr ffff888015b50240 by task poc/1219 Bug found and triaged by OpenAI Security Research and validated by Trail of Bits.
- 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
- 2.6.19affected
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before 785d908f8d21c8bc78b6fb2c2932ab662bf6918aaffected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before aedcfefdb5b7ed7f8a6196a3e68a25bdbe51d2f8affected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before 145812b678de9f3b59780173be3c0d22ed60dd93affected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before cc5bd568f9b7683e60841b6fd02c10d64535bd6eaffected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before 1c206d461c680c3151daa3c89fc26eaf5bf98a7faffected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before 680fbd7942185448eadb990a3d10a53eb946b702affected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before 14e812ab41df0cac033479da835ec9a5de633404affected · git
- 8814c4b533817df825485ff32ce6ac406c3a54d1 and later · before 0e243671bc7b8eaf00f83dd2f4367436dc0cff98affected · git
- before 2.6.19not 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 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-default | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-docs | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-ec2 | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-source | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-syms | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-trace | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-xen | before 3.0.101-108.223.1 | 3.0.101-108.223.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-74628Aug 22, 2026 · net/x25: fix use-after-free of the socket by its timers39Monitor
- ← EarlierCVE-2026-74629Aug 22, 2026 · net/dibs: Correct freeing of dmb_clientid_arr35Monitor
- Later →CVE-2026-74631Aug 22, 2026 · net: smc: fix splice entry lifetime imbalance in smc_rx_splice33Monitor
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 | 0e243671bc7b8eaf00f83dd2f4367436dc0cff98 | Vendor (CNA) |
| Linux Linux | 145812b678de9f3b59780173be3c0d22ed60dd93 | Vendor (CNA) |
| Linux Linux | 14e812ab41df0cac033479da835ec9a5de633404 | Vendor (CNA) |
| Linux Linux | 1c206d461c680c3151daa3c89fc26eaf5bf98a7f | Vendor (CNA) |
| Linux Linux | 680fbd7942185448eadb990a3d10a53eb946b702 | Vendor (CNA) |
| Linux Linux | 785d908f8d21c8bc78b6fb2c2932ab662bf6918a | Vendor (CNA) |
| Linux Linux | aedcfefdb5b7ed7f8a6196a3e68a25bdbe51d2f8 | Vendor (CNA) |
| Linux Linux | cc5bd568f9b7683e60841b6fd02c10d64535bd6e | 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) |
| suse:kernel-default | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-docs | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-ec2 | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-source | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-syms | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-trace | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-xen | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | 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/145812b678de9f3b59780173be3c0d22ed60dd93
- git.kernel.org/stable/c/14e812ab41df0cac033479da835ec9a5de633404
- git.kernel.org/stable/c/1c206d461c680c3151daa3c89fc26eaf5bf98a7f
- git.kernel.org/stable/c/680fbd7942185448eadb990a3d10a53eb946b702
- git.kernel.org/stable/c/785d908f8d21c8bc78b6fb2c2932ab662bf6918a
- git.kernel.org/stable/c/aedcfefdb5b7ed7f8a6196a3e68a25bdbe51d2f8
- git.kernel.org/stable/c/cc5bd568f9b7683e60841b6fd02c10d64535bd6e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.