CVE-2024-35890: gro: fix ownership transfer

Published May 19, 2024
·
Updated

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 skbsegmentlist those skbs can be reused as-is. This is an issue as their destructor was removed in skbgroreceivelist 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! (skborphan) RIP: 0010:ip6rcvcore+0x11bc/0x19a0 Call Trace: ipv6listrcv+0x250/0x3f0 netifreceiveskblistcore+0x49d/0x8f0 netifreceiveskblistinternal+0x634/0xd40 napicompletedone+0x1d2/0x7d0 grocellpoll+0x118/0x1f0

A similar construction is found in skbgroreceive, apply the same change there.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

gro: fix ownership transfer

The Linux kernel CVE team has assigned CVE-2024-35890 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051948-CVE-2024-35890-beaa@gregkh/T

Red Hat

Linux Kernel is vulnerable to a denial of service, caused by a ownership transfer issue if packets are GROed with fraglist. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service condition.

IBM

Affected Software

16 affected componentsFixes available
IBM Security Verify Governance<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Software Stack<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Virtual Appliance<=ISVG 10.0.2
IBM Security Verify Governance Identity Manager Container<=ISVG 10.0.2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
redhat/kernel<5.15.154
5.15.154
redhat/kernel<6.1.85
6.1.85
redhat/kernel<6.6.26
6.6.26
redhat/kernel<6.8.5
6.8.5
redhat/kernel<6.9
6.9
Linux Linux kernel>=5.15<5.15.154
Linux Linux kernel>=5.16<6.1.85
Linux Linux kernel>=6.2<6.6.26
Linux Linux kernel>=6.7<6.8.5
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2

Event History

May 19, 2024
CVE Published
via MITRE·08:34 AM
Data Sourced
via MITRE·08:34 AM
Description
Data Sourced
via NVD·09:15 AM
Description
Data Sourced
via NVD·09:15 AM
RemedySeverityAffected Software
May 20, 2024
Data Sourced
via Red Hat·11:48 AM
DescriptionSeverityAffected Software
Jul 11, 2024
Data Sourced
via Launchpad·07:46 PM
Description
Apr 27, 2025
Data Sourced
via Ubuntu·12:21 AM
RemedyDescriptionSeverityAffected Software
Aug 8, 57702
Event
via NVD·08:57 PM

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-35890?

CVE-2024-35890 has a high severity rating due to its potential impact on kernel operations.

2

How do I fix CVE-2024-35890?

To fix CVE-2024-35890, upgrade your kernel to version 5.15.154 or above, 6.1.85 or above, or 6.6.26 or above depending on your distribution.

3

What are the affected Linux kernel versions for CVE-2024-35890?

Affected versions for CVE-2024-35890 include kernel versions prior to 5.15.154, 6.1.85, 6.6.26, 6.8.5, and 6.9.

4

What impact does CVE-2024-35890 have on system security?

CVE-2024-35890 can lead to potential security risks by allowing misuse of memory segments in the kernel.

5

Who should be aware of CVE-2024-35890?

System administrators and users running affected versions of the Linux kernel should be aware of CVE-2024-35890 to ensure system security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203