CVE-2026-97599
Last modified
CVE-2026-97599 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: ieee802154: hwsim: serialize pib updates to fix double-free hwsim_update_pib() does an unserialized read-swap-free of phy->pib: pib_old = rtnl_dereference(phy->pib); ... rcu_assign_pointer(phy->pib, pib); kfree_rcu(pib_old, rcu); It assumes the RTNL is held, but ->set_channel is not always called under it: the mac802154 scan worker changes channels via drv_set_channel() without the RTNL. Such an update can race an RTNL-held one on the same phy; both read the same pib_old and both kfree_rcu() it, double-freeing the object.
Description
In the Linux kernel, the following vulnerability has been resolved: ieee802154: hwsim: serialize pib updates to fix double-free hwsim_update_pib() does an unserialized read-swap-free of phy->pib: pib_old = rtnl_dereference(phy->pib); ... rcu_assign_pointer(phy->pib, pib); kfree_rcu(pib_old, rcu); It assumes the RTNL is held, but ->set_channel is not always called under it: the mac802154 scan worker changes channels via drv_set_channel() without the RTNL. Such an update can race an RTNL-held one on the same phy; both read the same pib_old and both kfree_rcu() it, double-freeing the object. With SLUB percpu sheaves batching kfree_rcu(), this surfaces as a KASAN invalid-free in rcu_free_sheaf(). struct hwsim_phy has no lock for pib. Add one and make the swap atomic with rcu_replace_pointer() under it, dropping the misleading rtnl_dereference().
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= f25da51fdc381ca2863248c7060b3662632f0872, < 9973b3a67a7592a780ea12b08334539a900deec1; >= f25da51fdc381ca2863248c7060b3662632f0872, < d3b8f264ce09573aededd0a97dc41c8147797d8f; >= f25da51fdc381ca2863248c7060b3662632f0872, < db6442deecb1f13aeaf4f9d77746ea7555630fb3; >= f25da51fdc381ca2863248c7060b3662632f0872, < 979d5b8de8ed4e1f997aef12da5694b99be7b871 |
| Linux | Linux | 4.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97599?
How severe is CVE-2026-97599?
How do I fix CVE-2026-97599?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97593In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97594In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97595In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97596In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97597In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97598In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97600In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97601In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97602In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97603In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97604In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97605In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-97599?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
