Answer in brief
CVE-2026-46104 records a Medium severity (CVSS 5.5) vulnerability in selinux: use sk blob accessor in socket permission helpers. 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 5.5. 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 | >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <d350fef4bc2467fe1bce15f7a20fe60e01ce41ad || >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <7eca71f57f194c1638ebb7f4097d6be8fd04c101 || >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <032e70aff025d7c519af9ab791cd084380619263 | d350fef4bc2467fe1bce15f7a20fe60e01ce41ad, 7eca71f57f194c1638ebb7f4097d6be8fd04c101, 032e70aff025d7c519af9ab791cd084380619263 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: selinux: use sk blob accessor in socket permission helpers SELinux socket state lives in the composite LSM socket blob. sock_has_perm() and nlmsg_sock_has_extended_perms() currently dereference sk->sk_security directly, which assumes the SELinux socket blob is at offset zero. In stacked configurations that assumption does not hold. If another LSM allocates socket blob storage before SELinux, these helpers may read the wrong blob and feed invalid SID and class values into AVC checks. Use selinux_sock() instead of accessing sk->sk_security directly.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46104 records a Medium severity (CVSS 5.5) vulnerability in selinux: use sk blob accessor in socket permission helpers. 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 5.5. 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 | >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <d350fef4bc2467fe1bce15f7a20fe60e01ce41ad || >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <7eca71f57f194c1638ebb7f4097d6be8fd04c101 || >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <032e70aff025d7c519af9ab791cd084380619263 | d350fef4bc2467fe1bce15f7a20fe60e01ce41ad, 7eca71f57f194c1638ebb7f4097d6be8fd04c101, 032e70aff025d7c519af9ab791cd084380619263 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: selinux: use sk blob accessor in socket permission helpers SELinux socket state lives in the composite LSM socket blob. sock_has_perm() and nlmsg_sock_has_extended_perms() currently dereference sk->sk_security directly, which assumes the SELinux socket blob is at offset zero. In stacked configurations that assumption does not hold. If another LSM allocates socket blob storage before SELinux, these helpers may read the wrong blob and feed invalid SID and class values into AVC checks. Use selinux_sock() instead of accessing sk->sk_security directly.
Quoted source text, attributed separately from HOL analysis.