Answer in brief
CVE-2026-99048 records a Unknown severity vulnerability in gve: fix napi_disable deadlock when attempting to disable XSK pools. 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 | >=606048cbd8346e616cfaee01b0143d072534136d <42935a61001927aa01db10b53b420efd37eaa99b || >=606048cbd8346e616cfaee01b0143d072534136d <3d377911ce81fd4e61af814e750d8e08879a5208 || >=606048cbd8346e616cfaee01b0143d072534136d <0cb6939a4dfefa822007b7a71986e06bc4f61f54 | 42935a61001927aa01db10b53b420efd37eaa99b, 3d377911ce81fd4e61af814e750d8e08879a5208, 0cb6939a4dfefa822007b7a71986e06bc4f61f54 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
In the Linux kernel, the following vulnerability has been resolved: gve: fix napi_disable deadlock when attempting to disable XSK pools When disabling XSK pools, GVE calls the unlocked versions of napi_disable and napi_enable. However, the netdev lock has already been acquired before ndo_bpf is called because GVE supports queue management ops. Calling the unlocked versions of napi_disable/enable results in a deadlock when attempting to disable XSK pools, as the thread attempts to re-acquire a lock it already holds. Update the NAPI calls to use the locked versions. This issue was found in production.
Quoted source text, attributed separately from HOL analysis.