Answer in brief
CVE-2024-46762 records a Unknown severity vulnerability in xen: privcmd: Fix possible access to a freed kirqfd instance. 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 | >=f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 <e997b357b13a7d95de31681fc54fcc34235fa527 || >=f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 <112fd2f02b308564724b8e81006c254d20945c4b || >=f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 <611ff1b1ae989a7bcce3e2a8e132ee30e968c557 | e997b357b13a7d95de31681fc54fcc34235fa527, 112fd2f02b308564724b8e81006c254d20945c4b, 611ff1b1ae989a7bcce3e2a8e132ee30e968c557 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Sep 18, 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: xen: privcmd: Fix possible access to a freed kirqfd instance Nothing prevents simultaneous ioctl calls to privcmd_irqfd_assign() and privcmd_irqfd_deassign(). If that happens, it is possible that a kirqfd created and added to the irqfds_list by privcmd_irqfd_assign() may get removed by another thread executing privcmd_irqfd_deassign(), while the former is still using it after dropping the locks. This can lead to a situation where an already freed kirqfd instance may be accessed and cause kernel oops. Use SRCU locking to prevent the same, as is done for the KVM implementation for irqfds.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-46762 records a Unknown severity vulnerability in xen: privcmd: Fix possible access to a freed kirqfd instance. 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 | >=f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 <e997b357b13a7d95de31681fc54fcc34235fa527 || >=f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 <112fd2f02b308564724b8e81006c254d20945c4b || >=f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 <611ff1b1ae989a7bcce3e2a8e132ee30e968c557 | e997b357b13a7d95de31681fc54fcc34235fa527, 112fd2f02b308564724b8e81006c254d20945c4b, 611ff1b1ae989a7bcce3e2a8e132ee30e968c557 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Sep 18, 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: xen: privcmd: Fix possible access to a freed kirqfd instance Nothing prevents simultaneous ioctl calls to privcmd_irqfd_assign() and privcmd_irqfd_deassign(). If that happens, it is possible that a kirqfd created and added to the irqfds_list by privcmd_irqfd_assign() may get removed by another thread executing privcmd_irqfd_deassign(), while the former is still using it after dropping the locks. This can lead to a situation where an already freed kirqfd instance may be accessed and cause kernel oops. Use SRCU locking to prevent the same, as is done for the KVM implementation for irqfds.
Quoted source text, attributed separately from HOL analysis.