CVE-2025-21980
What it is
In the Linux kernel, the following vulnerability has been resolved: sched: address a potential NULL pointer dereference in the GRED scheduler. If kzalloc in gred_init returns a NULL pointer, the code follows the error handling path, invoking gred_destroy. This, in turn, calls gred_offload, where memset could receive a NULL pointer as input, potentially leading to a kernel crash. When table->opt is NULL in gred_init(), gred_change_table_def() is not called yet, so it is not necessary to call ->ndo_setup_tc() in gred_offload().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 6.1.132
- Linux Kernel < 6.6.84
- Linux Kernel < 6.12.20
- Linux Kernel < 6.13.8
- Linux Kernel 6.14
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-21980.md and follow it. Check whether this project is affected by CVE-2025-21980. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0f0a152957d64ce45b4c27c687e7d087e8f45079
- https://git.kernel.org/stable/c/115ef44a98220fddfab37a39a19370497cd718b9
- https://git.kernel.org/stable/c/5f996b4f80c2cef1f9c77275055e7fcba44c9199
- https://git.kernel.org/stable/c/68896dd50180b38ea552e49a6a00b685321e5769
- https://git.kernel.org/stable/c/d02c9acd68950a444acda18d514e2b41f846cb7f
References
- https://git.kernel.org/stable/c/0f0a152957d64ce45b4c27c687e7d087e8f45079
- https://git.kernel.org/stable/c/115ef44a98220fddfab37a39a19370497cd718b9
- https://git.kernel.org/stable/c/5f996b4f80c2cef1f9c77275055e7fcba44c9199
- https://git.kernel.org/stable/c/68896dd50180b38ea552e49a6a00b685321e5769
- https://git.kernel.org/stable/c/d02c9acd68950a444acda18d514e2b41f846cb7f
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html