Kernel memory corruption via stale traffic-control callback
Published Dec 30, 2025 · Updated Dec 30, 2025
Use-after-free in the Linux kernel 5.3 through 6.3 allows local users to corrupt kernel memory through tc qdisc configuration. The tcf_block_bind error path frees callback objects after ndo_setup_tc has linked them into driver_list, leaving dangling entries that flow_block_cb_setup_simple later dereferences. Low-privilege local access with CAP_NET_ADMIN obtainable in a new network namespace is sufficient; exploitation can disclose or modify kernel memory or panic the system.
Summary
What happened
Use-after-free in the Linux kernel 5.3 through 6.3 allows local users to corrupt kernel memory through tc qdisc configuration. The tcf_block_bind error path frees callback objects after ndo_setup_tc has linked them into driver_list, leaving dangling entries that flow_block_cb_setup_simple later dereferences. Low-privilege local access with CAP_NET_ADMIN obtainable in a new network namespace is sufficient; exploitation can disclose or modify kernel memory or panic the system.
The record
- CVE
- CVE-2023-54193
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.3
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <26aec72429a05e917d574eca0efc5306c63a8862
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <55866fe3fded3ce94ac3fc1bb3dfce654282f483
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <7311c8be3755611bf6edea4dfbeb190b4bdd489f
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <7b7a74ed303d532fb73ae4b1697f16a0fea89cd0
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <cb145932fcf6814e7e95e467eb70e7849a845ae9
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <cc5fe387c6294d0471cb7ed064efac97fac65ccc
- Affected versionversion=59094b1e5094c7e50a3d2912202fd30b6a1dadf8 <da94a7781fc3c92e7df7832bc2746f4d39bc624e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo