VulnerabilityPublished 18 Oct 2026Updated 21 Oct 2026

CVE-2026-98544: Linux kernel · bna: prevent IOC timer rearm during teardown

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f04cbdfac9b8284146995ab7ba0d054ad1d20ec6 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f04cbdfac9b8284146995ab7ba0d054ad1d20ec6, e09d1c6729ee4a7812128902d9274ff565f958b8, 77b1718e39e5c9f6956fb60807326af20baf889d +2

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1d32f7696286eef9e5644eb57e79a36756274357, < f04cbdfac9b8284146995ab7ba0d054ad1d20ec6	Fixed in f04cbdfac9b8284146995ab7ba0d054ad1d20ec6
LinuxLinux	Affected ≥ 1d32f7696286eef9e5644eb57e79a36756274357, < e09d1c6729ee4a7812128902d9274ff565f958b8	Fixed in e09d1c6729ee4a7812128902d9274ff565f958b8
LinuxLinux	Affected ≥ 1d32f7696286eef9e5644eb57e79a36756274357, < 77b1718e39e5c9f6956fb60807326af20baf889d	Fixed in 77b1718e39e5c9f6956fb60807326af20baf889d
LinuxLinux	Affected ≥ 1d32f7696286eef9e5644eb57e79a36756274357, < 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a	Fixed in 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a
LinuxLinux	Affected ≥ 1d32f7696286eef9e5644eb57e79a36756274357, < 4d97a141e85a034566c33c7ed854c8a3e8a268f1	Fixed in 4d97a141e85a034566c33c7ed854c8a3e8a268f1
LinuxLinux	Affected =2.6.38	Fixed in–

Description

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.

References

Community reviews

Loading reviews…