Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35890: gro: fix ownership transfer

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2eeab8c47c3c0276e0746bc382f405c9a236a5ad, 5b3b67f731296027cceb3efad881ae281213f86f, d225b0ac96dc40d7e8ae2bc227eb2c56e130975f.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2eeab8c47c3c0276e0746bc382f405c9a236a5ad, 5b3b67f731296027cceb3efad881ae281213f86f, d225b0ac96dc40d7e8ae2bc227eb2c56e130975f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: gro: fix ownership transfer If packets are GROed with fraglist they might be segmented later on and continue their journey in the stack. In skb_segment_list those skbs can be reused as-is. This is an issue as their destructor was removed in skb_gro_receive_list but not the reference to their socket, and then they can't be orphaned. Fix this by also removing the reference to the socket. For example this could be observed, kernel BUG at include/linux/skbuff.h:3131! (skb_orphan) RIP: 0010:ip6_rcv_core+0x11bc/0x19a0 Call Trace: ipv6_list_rcv+0x250/0x3f0 __netif_receive_skb_list_core+0x49d/0x8f0 netif_receive_skb_list_internal+0x634/0xd40 napi_complete_done+0x1d2/0x7d0 gro_cell_poll+0x118/0x1f0 A similar construction is found in skb_gro_receive, apply the same change there.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 19, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35890

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15 and later · before 5.15.154
  • linux linux kernel5.16 and later · before 6.1.85
  • linux linux kernel6.2 and later · before 6.6.26
  • linux linux kernel6.7 and later · before 6.8.5
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • 5e10da5385d20c4bae587bc2921e5fdd9655d5fc and later · before d225b0ac96dc40d7e8ae2bc227eb2c56e130975faffected · git
    • 5e10da5385d20c4bae587bc2921e5fdd9655d5fc and later · before 2eeab8c47c3c0276e0746bc382f405c9a236a5adaffected · git
    • 5e10da5385d20c4bae587bc2921e5fdd9655d5fc and later · before fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6affected · git
    • 5e10da5385d20c4bae587bc2921e5fdd9655d5fc and later · before 5b3b67f731296027cceb3efad881ae281213f86faffected · git
    • 5e10da5385d20c4bae587bc2921e5fdd9655d5fc and later · before ed4cccef64c1d0d5b91e69f7a8a6697c3a865486affected · git
    • before 5.15not affected · semver
    • 5.15.154 and later · up to and including 5.15.*not affected · semver
    • 6.1.85 and later · up to and including 6.1.*not affected · semver
    • 6.6.26 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.18.1.el9_47.3.0-427.18.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.18.1.el9_45.14.0-427.18.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35887May 19, 2024 · ax25: fix use-after-free bugs caused by ax25_ds_del_timer
    31Monitor
  • ← EarlierCVE-2024-35889May 19, 2024 · idpf: fix kernel panic on unknown packet types
    22Monitor
  • Later →CVE-2024-35891May 19, 2024 · net: phy: micrel: Fix potential null pointer dereference
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2eeab8c47c3c0276e0746bc382f405c9a236a5adVendor (CNA)
Linux Linux5b3b67f731296027cceb3efad881ae281213f86fVendor (CNA)
Linux Linuxd225b0ac96dc40d7e8ae2bc227eb2c56e130975fVendor (CNA)
Linux Linuxed4cccef64c1d0d5b91e69f7a8a6697c3a865486Vendor (CNA)
Linux Linuxfc126c1d51e9552eacd2d717b9ffe9262a8a4cd6Vendor (CNA)
almalinux:bpftool7.3.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.18.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-372.133.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records