Answer in brief
CVE-2022-50490 records a High severity (CVSS 7.1) vulnerability in bpf: Propagate error from htab_lock_bucket() to userspace. 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.
CVSS is 7.1. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <0e13425104903970a5ede853082d3bbb4edec6f3 || >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <6bfee6eb3d6b96ae730a542909dd22b5f9f50d58 || >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <4f1f39a8f1ce1b24fee6852d7dcd704ce7c4334d || >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <66a7a92e4d0d091e79148a4c6ec15d1da65f4280 | 0e13425104903970a5ede853082d3bbb4edec6f3, 6bfee6eb3d6b96ae730a542909dd22b5f9f50d58, 4f1f39a8f1ce1b24fee6852d7dcd704ce7c4334d, 66a7a92e4d0d091e79148a4c6ec15d1da65f4280 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: Propagate error from htab_lock_bucket() to userspace In __htab_map_lookup_and_delete_batch() if htab_lock_bucket() returns -EBUSY, it will go to next bucket. Going to next bucket may not only skip the elements in current bucket silently, but also incur out-of-bound memory access or expose kernel memory to userspace if current bucket_cnt is greater than bucket_size or zero. Fixing it by stopping batch operation and returning -EBUSY when htab_lock_bucket() fails, and the application can retry or skip the busy batch as needed.
Quoted source text, attributed separately from HOL analysis.