Answer in brief
CVE-2024-35890 records a Unknown severity vulnerability in gro: fix ownership transfer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <d225b0ac96dc40d7e8ae2bc227eb2c56e130975f || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <2eeab8c47c3c0276e0746bc382f405c9a236a5ad || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6 || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <5b3b67f731296027cceb3efad881ae281213f86f || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 | d225b0ac96dc40d7e8ae2bc227eb2c56e130975f, 2eeab8c47c3c0276e0746bc382f405c9a236a5ad, fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6, 5b3b67f731296027cceb3efad881ae281213f86f, ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
May 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-35890 records a Unknown severity vulnerability in gro: fix ownership transfer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <d225b0ac96dc40d7e8ae2bc227eb2c56e130975f || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <2eeab8c47c3c0276e0746bc382f405c9a236a5ad || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6 || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <5b3b67f731296027cceb3efad881ae281213f86f || >=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 | d225b0ac96dc40d7e8ae2bc227eb2c56e130975f, 2eeab8c47c3c0276e0746bc382f405c9a236a5ad, fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6, 5b3b67f731296027cceb3efad881ae281213f86f, ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
May 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.