Answer in brief
CVE-2024-36883 records a Unknown severity vulnerability in net: fix out-of-bounds access in ops_init. 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.
Answer in brief
CVE-2024-36883 records a Unknown severity vulnerability in net: fix out-of-bounds access in ops_init. 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 | >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <3cdc34d76c4f777579e28ad373979d36c030cfd3 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <7b0e64583eab8c1d896b47e5dd0bf2e7d86ec41f || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <0c3248bc708a7797be573214065cf908ff1f54c7 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <9518b79bfd2fbf99fa9b7e8e36bcb1825e7ba030 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <2d60ff5874aefd006717ca5e22ac1e25eac29c42 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <b6dbfd5bcc267a95a0bf1bf96af46243f96ec6cd || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <f4f94587e1bf87cb40ec33955a9d90148dd026ab || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <a26ff37e624d12e28077e5b24d2b264f62764ad6 || 561331eae0a03d0c4cf60f3cf485aa3e8aa5ab48 || a2c82f7bee1ffa9eafa1fb0bd886a7eea8c9e497 || >=3.0.19 <3.1 || >=3.2.3 <3.3 | 3cdc34d76c4f777579e28ad373979d36c030cfd3, 7b0e64583eab8c1d896b47e5dd0bf2e7d86ec41f, 0c3248bc708a7797be573214065cf908ff1f54c7, 9518b79bfd2fbf99fa9b7e8e36bcb1825e7ba030, 2d60ff5874aefd006717ca5e22ac1e25eac29c42, b6dbfd5bcc267a95a0bf1bf96af46243f96ec6cd, f4f94587e1bf87cb40ec33955a9d90148dd026ab, a26ff37e624d12e28077e5b24d2b264f62764ad6, 3.1, 3.3 |
| Linux/Linuxgeneric | 3.3 | Not reported |
Published upstream
May 30, 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: net: fix out-of-bounds access in ops_init net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is read twice, first to allocate an array, then to set s.len, which is later used to limit the bounds of the array access. It is possible that the array is allocated and another thread is registering a new pernet ops, increments max_gen_ptrs, which is then used to set s.len with a larger than allocated length for the variable array. Fix it by reading max_gen_ptrs only once in net_alloc_generic. If max_gen_ptrs is later incremented, it will be caught in net_assign_generic.
Quoted source text, attributed separately from HOL analysis.
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 | >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <3cdc34d76c4f777579e28ad373979d36c030cfd3 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <7b0e64583eab8c1d896b47e5dd0bf2e7d86ec41f || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <0c3248bc708a7797be573214065cf908ff1f54c7 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <9518b79bfd2fbf99fa9b7e8e36bcb1825e7ba030 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <2d60ff5874aefd006717ca5e22ac1e25eac29c42 || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <b6dbfd5bcc267a95a0bf1bf96af46243f96ec6cd || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <f4f94587e1bf87cb40ec33955a9d90148dd026ab || >=073862ba5d249c20bd5c49fc6d904ff0e1f6a672 <a26ff37e624d12e28077e5b24d2b264f62764ad6 || 561331eae0a03d0c4cf60f3cf485aa3e8aa5ab48 || a2c82f7bee1ffa9eafa1fb0bd886a7eea8c9e497 || >=3.0.19 <3.1 || >=3.2.3 <3.3 | 3cdc34d76c4f777579e28ad373979d36c030cfd3, 7b0e64583eab8c1d896b47e5dd0bf2e7d86ec41f, 0c3248bc708a7797be573214065cf908ff1f54c7, 9518b79bfd2fbf99fa9b7e8e36bcb1825e7ba030, 2d60ff5874aefd006717ca5e22ac1e25eac29c42, b6dbfd5bcc267a95a0bf1bf96af46243f96ec6cd, f4f94587e1bf87cb40ec33955a9d90148dd026ab, a26ff37e624d12e28077e5b24d2b264f62764ad6, 3.1, 3.3 |
| Linux/Linuxgeneric | 3.3 | Not reported |
Published upstream
May 30, 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: net: fix out-of-bounds access in ops_init net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is read twice, first to allocate an array, then to set s.len, which is later used to limit the bounds of the array access. It is possible that the array is allocated and another thread is registering a new pernet ops, increments max_gen_ptrs, which is then used to set s.len with a larger than allocated length for the variable array. Fix it by reading max_gen_ptrs only once in net_alloc_generic. If max_gen_ptrs is later incremented, it will be caught in net_assign_generic.
Quoted source text, attributed separately from HOL analysis.