CVE-2025-21980: sched: address a potential NULL pointer dereference in the GRED scheduler.
First published: Tue Apr 01 2025(Updated: )
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().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/d02c9acd68950a444acda18d514e2b41f846cb7f
- https://git.kernel.org/stable/c/0f0a152957d64ce45b4c27c687e7d087e8f45079
- https://git.kernel.org/stable/c/68896dd50180b38ea552e49a6a00b685321e5769
- https://git.kernel.org/stable/c/5f996b4f80c2cef1f9c77275055e7fcba44c9199
- https://git.kernel.org/stable/c/115ef44a98220fddfab37a39a19370497cd718b9
Frequently Asked Questions
What is the severity of CVE-2025-21980?
CVE-2025-21980 has been classified as a moderate severity vulnerability due to the potential for a NULL pointer dereference in the GRED scheduler.
How do I fix CVE-2025-21980?
To address CVE-2025-21980, update to the latest version of the Linux kernel that includes the fix for this vulnerability.
What are the potential impacts of CVE-2025-21980?
The potential impact of CVE-2025-21980 includes system instability or crashes due to NULL pointer dereference in the GRED scheduler.
Which versions of the Linux kernel are affected by CVE-2025-21980?
CVE-2025-21980 affects various versions of the Linux kernel prior to the fix being implemented in subsequent releases.
Is there a workaround for CVE-2025-21980?
There are no recommended workarounds for CVE-2025-21980; updating the kernel is the primary response for mitigation.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/title
- agent/description
- agent/type
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/source
- agent/author
- agent/last-modified-date
- agent/tags
- agent/event
- vendor/linux
- canonical/linux kernel