CVE-2026-98544: bna: prevent IOC timer rearm during teardown
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a, 3614582375fc4407e09ff42ff178a045e2fe6e8f, 4d97a141e85a034566c33c7ed854c8a3e8a268f1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a, 3614582375fc4407e09ff42ff178a045e2fe6e8f, 4d97a141e85a034566c33c7ed854c8a3e8a268f1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: bna: prevent IOC timer rearm during teardown bna: prevent IOC timer rearm during teardown bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer. bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad. Deleting iocpf_timer last does not fix this. sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live. Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored. This issue was identified during our ongoing static-analysis research while reviewing kernel code.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 9th 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.2%
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.38affected
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before 8160cd1ec527caedd36c36f948234e834cd086e6affected · git
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before 3614582375fc4407e09ff42ff178a045e2fe6e8faffected · git
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before f04cbdfac9b8284146995ab7ba0d054ad1d20ec6affected · git
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before 28e32ace754b57534ef0ca0fb99bcbea5b13ba2aaffected · git
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before 4d97a141e85a034566c33c7ed854c8a3e8a268f1affected · git
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before e09d1c6729ee4a7812128902d9274ff565f958b8affected · git
- 1d32f7696286eef9e5644eb57e79a36756274357 and later · before 77b1718e39e5c9f6956fb60807326af20baf889daffected · git
- before 2.6.38not affected · semver
- 5.15.224 and later · up to and including 5.15.*not 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 | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.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-98542Oct 18, 2026 · cgroup/cpuset: Return PERR_NOCPUS in remote_partition_enable() on subpartitions_cpus conflict0Monitor
- ← EarlierCVE-2026-98543Oct 18, 2026 · bpf: fs/xattr: don't assume the inode is locked in path_unlink/path_rmdir29Monitor
- Later →CVE-2026-98545Oct 18, 2026 · ata: libata-scsi: bound the ATA passthru sense descriptor writes0Monitor
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 | 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a | Vendor (CNA) |
| Linux Linux | 3614582375fc4407e09ff42ff178a045e2fe6e8f | Vendor (CNA) |
| Linux Linux | 4d97a141e85a034566c33c7ed854c8a3e8a268f1 | Vendor (CNA) |
| Linux Linux | 77b1718e39e5c9f6956fb60807326af20baf889d | Vendor (CNA) |
| Linux Linux | 8160cd1ec527caedd36c36f948234e834cd086e6 | Vendor (CNA) |
| Linux Linux | e09d1c6729ee4a7812128902d9274ff565f958b8 | Vendor (CNA) |
| Linux Linux | f04cbdfac9b8284146995ab7ba0d054ad1d20ec6 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayOct 31, 2026+12 d
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-1351 · Oct 19, 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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3614582375fc4407e09ff42ff178a045e2fe6e8f
- git.kernel.org/stable/c/4d97a141e85a034566c33c7ed854c8a3e8a268f1
- git.kernel.org/stable/c/77b1718e39e5c9f6956fb60807326af20baf889d
- git.kernel.org/stable/c/8160cd1ec527caedd36c36f948234e834cd086e6
- git.kernel.org/stable/c/e09d1c6729ee4a7812128902d9274ff565f958b8
- git.kernel.org/stable/c/f04cbdfac9b8284146995ab7ba0d054ad1d20ec6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.