Freed-memory read via final-channel teardown
Published May 22, 2024 · Updated May 11, 2026
Use-after-free in the Linux kernel peak_pci CAN driver allows local users to access freed memory during module removal. On the final channel, peak_pci_remove frees the network device that owns chan and then dereferences chan->pciec_card. Triggering requires local removal of the peak_pci module; the published evidence confirms an eight-byte post-free read but does not establish a reliable further consequence.
Summary
What happened
Use-after-free in the Linux kernel peak_pci CAN driver allows local users to access freed memory during module removal. On the final channel, peak_pci_remove frees the network device that owns chan and then dereferences chan->pciec_card. Triggering requires local removal of the peak_pci module; the published evidence confirms an eight-byte post-free read but does not establish a reliable further consequence.
The record
- CVE
- CVE-2021-47456
- Published
- May 22, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=3.4
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <0e5afdc2315b0737edcf55bede4ee1640d2d464d
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <1248582e47a9f7ce0ecd156c39fc61f8b6aa3699
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <1c616528ba4aeb1125a06b407572ab7b56acae38
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <28f28e4bc3a5e0051faa963f10b778ab38c1db69
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <34914971bb3244db4ce2be44e9438a9b30c56250
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <447d44cd2f67a20b596ede3ca3cd67086dfd9ca9
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <949fe9b35570361bc6ee2652f89a0561b26eec98
- Affected versionversion=e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd <adbda14730aacce41c0d3596415aa39ad63eafd9
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