Skip to main content
VulnerabilityPublished Updated

CVE-2025-38122: Linux kernel · gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c741a7ef68023ac800054e2131c3e22e647fd7e3 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:23 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in c741a7ef68023ac800054e2131c3e22e647fd7e3, ae98a1787fdcb0096d122bc80d93c3c7d812c04b, a0319c9b1648a67511e947a596ca86888451c0a7 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a57e5de476be0b4b7f42beb6a21c19ad9c577aa3, < c741a7ef68023ac800054e2131c3e22e647fd7e3
Fixed in
  • c741a7ef68023ac800054e2131c3e22e647fd7e3
LinuxLinuxAffected
  • ≥ a57e5de476be0b4b7f42beb6a21c19ad9c577aa3, < ae98a1787fdcb0096d122bc80d93c3c7d812c04b
Fixed in
  • ae98a1787fdcb0096d122bc80d93c3c7d812c04b
LinuxLinuxAffected
  • ≥ a57e5de476be0b4b7f42beb6a21c19ad9c577aa3, < a0319c9b1648a67511e947a596ca86888451c0a7
Fixed in
  • a0319c9b1648a67511e947a596ca86888451c0a7
LinuxLinuxAffected
  • ≥ a57e5de476be0b4b7f42beb6a21c19ad9c577aa3, < 12c331b29c7397ac3b03584e12902990693bc248
Fixed in
  • 12c331b29c7397ac3b03584e12902990693bc248
LinuxLinuxAffected
  • ≥ a57e5de476be0b4b7f42beb6a21c19ad9c577aa3, < 7f6265fce3bd424ded666481b37f106d7915fb6b
Fixed in
  • 7f6265fce3bd424ded666481b37f106d7915fb6b
LinuxLinuxAffected
  • ≥ a57e5de476be0b4b7f42beb6a21c19ad9c577aa3, < 2e5ead9e4e91fbe7799bd38afd8904543be1cb51
Fixed in
  • 2e5ead9e4e91fbe7799bd38afd8904543be1cb51

Description

In the Linux kernel, the following vulnerability has been resolved: gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO gve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo() did not check for this case before dereferencing the returned pointer. Add a missing NULL check to prevent a potential NULL pointer dereference when allocation fails. This improves robustness in low-memory scenarios.

References

Community reviews

Loading reviews…