CVE-2026-98008: net: macb: fix NULL pointer dereference on unbind with fixed-link
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 054ad8e66025eb4778d840bef80c270646cebcd2, 38b6be101006d3e7af972999f45d4f1e8250587a, 5.11; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 054ad8e66025eb4778d840bef80c270646cebcd2, 38b6be101006d3e7af972999f45d4f1e8250587a, 5.11; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: net: macb: fix NULL pointer dereference on unbind with fixed-link When the device tree describes a fixed-link and has no "mdio" child node, macb_mii_init() returns early without allocating the MDIO bus, leaving bp->mii_bus as NULL. Two cleanup paths then dereference this NULL bus: 1. On driver unbind, macb_remove() unconditionally calls mdiobus_unregister(bp->mii_bus), which oopses: Unable to handle kernel NULL pointer dereference at virtual address 00000000000004a8 pc : mdiobus_unregister+0x14/0xa4 lr : macb_remove+0x38/0xa4 Call trace: mdiobus_unregister+0x14/0xa4 (P) macb_remove+0x38/0xa4 platform_remove+0x20/0x30 device_release_driver_internal+0x1c8/0x224 unbind_store+0xb4/0xbc 2. On the probe error path in macb_probe(), reached when macb_mii_init() has succeeded but a subsequent step fails, the err_out_unregister_mdio label runs the same unconditional cleanup. mdiobus_unregister() and mdiobus_free() do not guard against a NULL bus, so guard the calls in both macb_remove() and the probe error path.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- cafa5942bd2df3d80e3eeb2deb4bc050f7761f3d, c81dcaa9cd0b66816c2ecb6c5df0b6afde9c7da5, 19088c5378c9fea54e552d8bc7418a3aa1e06990, 6.12affected
- 831e19e565b5210930fa183730071f8290c61263 and later · before afa224cabc0132ca414b9141b1a919ca2d318cd0affected · git
- 81db1e52848694761a1aa162ce76198af9964ed8 and later · before 054ad8e66025eb4778d840bef80c270646cebcd2affected · git
- d0c3601f2c4e12e7689b0f46ebc17525250ea8c3 and later · before f737d999fcb8f276d77b01ea4c2016ee01dad19baffected · git
- d0c3601f2c4e12e7689b0f46ebc17525250ea8c3 and later · before 5710f6a74f63cbba0e15cd75917234916181c9d4affected · git
- d0c3601f2c4e12e7689b0f46ebc17525250ea8c3 and later · before edb39c7666bb3924da761dfb417db85c1e5d8ad3affected · git
- d0c3601f2c4e12e7689b0f46ebc17525250ea8c3 and later · before 38b6be101006d3e7af972999f45d4f1e8250587aaffected · git
- 6.1.114 and later · before 6.1.189affected · semver
- 6.6.58 and later · before 6.6.158affected · semver
- 5.10.228 and later · before 5.11affected · 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-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-98006Sep 25, 2026 · ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev0Monitor
- ← EarlierCVE-2026-98007Sep 25, 2026 · bpf: Reject non-scalar bpf_loop iteration counts0Monitor
- Later →CVE-2026-98009Sep 25, 2026 · net/sched: ets: clamp quantum in parse and fallback paths0Monitor
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 | 054ad8e66025eb4778d840bef80c270646cebcd2 | Vendor (CNA) |
| Linux Linux | 38b6be101006d3e7af972999f45d4f1e8250587a | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5710f6a74f63cbba0e15cd75917234916181c9d4 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.12 | Vendor (CNA) |
| Linux Linux | 6.6.158 | Vendor (CNA) |
| Linux Linux | afa224cabc0132ca414b9141b1a919ca2d318cd0 | Vendor (CNA) |
| Linux Linux | edb39c7666bb3924da761dfb417db85c1e5d8ad3 | Vendor (CNA) |
| Linux Linux | f737d999fcb8f276d77b01ea4c2016ee01dad19b | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
Show all references (5 more)Show less
- git.kernel.org/stable/c/38b6be101006d3e7af972999f45d4f1e8250587a
- git.kernel.org/stable/c/5710f6a74f63cbba0e15cd75917234916181c9d4
- git.kernel.org/stable/c/afa224cabc0132ca414b9141b1a919ca2d318cd0
- git.kernel.org/stable/c/edb39c7666bb3924da761dfb417db85c1e5d8ad3
- git.kernel.org/stable/c/f737d999fcb8f276d77b01ea4c2016ee01dad19b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.