Kernel warning via negative IRQ mishandling
Published Feb 27, 2025 · Updated May 11, 2026
Improper IRQ validation in the Linux kernel's TI AM65 CPSW driver allows local users to trigger a kernel warning through channel changes. am65_cpsw_nuss_remove_tx_chns() treats a negative k3_udma_glue_tx_get_irq() error as valid because it checks for nonzero rather than a positive IRQ, then attempts to free that invalid value. The sequence requires privileged local channel reconfiguration, a transmit-channel initialization failure, and a later request for more channels; the reported result is a kernel warning.
Summary
What happened
Improper IRQ validation in the Linux kernel's TI AM65 CPSW driver allows local users to trigger a kernel warning through channel changes. am65_cpsw_nuss_remove_tx_chns() treats a negative k3_udma_glue_tx_get_irq() error as valid because it checks for nonzero rather than a positive IRQ, then attempts to free that invalid value. The sequence requires privileged local channel reconfiguration, a transmit-channel initialization failure, and a later request for more channels; the reported result is a kernel warning.
The record
- CVE
- CVE-2025-21799
- Published
- Feb 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE 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=5.7
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <321990fdf4f1bb64e818c7140688bf33d129e48d
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <4395a44acb15850e492dd1de9ec4b6479d96bc80
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <8448c87b3af68bebca21e3136913f7f77e363515
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <88fd5db8c0073bd91d18391feb5741aeb0a2b475
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <8aae91ae1c65782a169ec070e023d4d269e5d6e6
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <aea5cca681d268f794fa2385f9ec26a5cce025cd
- Affected versionversion=93a76530316a3d8cc2d82c3deca48424fee92100 <ed8c0300f302338c36edb06bca99051e5be6fb2f
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