Kernel memory corruption via stale si470x callback context
Published Oct 7, 2025 · Updated Oct 7, 2025
Use-after-free in the Linux kernel si470x USB radio driver allows local users to cause unspecified impact during device initialization. When si470x_start() fails after usb_submit_urb(), the probe path frees the si470x_device without killing the submitted URB, so its callback later dereferences the freed context. Triggering requires Si470x USB device initialization and the post-submission failure path; no concrete exploit consequence is published.
Summary
What happened
Use-after-free in the Linux kernel si470x USB radio driver allows local users to cause unspecified impact during device initialization. When si470x_start() fails after usb_submit_urb(), the probe path frees the si470x_device without killing the submitted URB, so its callback later dereferences the freed context. Triggering requires Si470x USB device initialization and the post-submission failure path; no concrete exploit consequence is published.
The record
- CVE
- CVE-2022-50542
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0ca298d548461d29615f9a2b1309e8dcf4a352c6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <146bd005ebb01ae190c22af050cb98623958c373
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1c6447d0fc68650e51586dde79b5090d9d77f13a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <52f54fe78cca24850a30865037250f63eb3d5bf7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63648a7bd1a7599bcc2040a6d1792363ae4c2e1b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6c8aee0c8fcc6dda94315f7908e8fa9bc75abe75
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d21e0b1b41b21d628bf2afce777727bd4479aa5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8c6151b8e8dd2d98ad2cd725d26d1e103d989891
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92b0888398e4ba51d93b618a6506781f4e3879c9
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