eventfs: Fix use-after-free in eventfs_remove_rec() (CVE-2026-74606) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-74606

eventfs: Fix use-after-free in eventfs_remove_rec()

Answer in brief

CVE-2026-74606 records a Unknown severity vulnerability in eventfs: Fix use-after-free in eventfs_remove_rec(). 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.

Published Aug 22, 2026Updated Aug 22, 2026Source checked Aug 22, 2026First seen by HOL Aug 22, 2026Material review Aug 22, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=5dfb04100326f70e3b2d2872c2476ed20b804837 <b77581b25e213e83b79ce11eb30024e55ceeb3e9 \|\| >=43aa6f97c2d03a52c1ddb86768575fc84344bdbb <f161d7861a0bfdf10af6b738b3b57636204661fb \|\| >=43aa6f97c2d03a52c1ddb86768575fc84344bdbb <5635211b44969f4816e29ec4d5f8665fb39535d0 \|\| >=43aa6f97c2d03a52c1ddb86768575fc84344bdbb <74bb1eaf72d185a78c879eb2678ea500f82f46a8 \|\| >=43aa6f97c2d03a52c1ddb86768575fc84344bdbb <fd73b691702170d37d66f4b0278530cea8ed419a \|\| 5a43badefe0eccca0c26144c0a44b8d417ce8103 \|\| >=6.6.18 <6.6.152 \|\| >=6.7.6 <6.8	b77581b25e213e83b79ce11eb30024e55ceeb3e9, f161d7861a0bfdf10af6b738b3b57636204661fb, 5635211b44969f4816e29ec4d5f8665fb39535d0, 74bb1eaf72d185a78c879eb2678ea500f82f46a8, fd73b691702170d37d66f4b0278530cea8ed419a, 6.6.152, 6.8
Linux/Linuxgeneric	6.8	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to b77581b25e213e83b79ce11eb30024e55ceeb3e9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 22, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: eventfs: Fix use-after-free in eventfs_remove_rec() eventfs_remove_rec() recursively removes the child at the current loop position. After the recursive call returns, list_for_each_entry() advances by reading list.next from the removed child. If free_ei() drops the final reference, release_ei() reuses the list/rcu union to queue an SRCU callback. The child may be freed before that read. The eventfs_mutex serializes list updates, but it does not keep the removed child alive or prevent the SRCU callback from running. Use list_for_each_entry_safe() to save the next sibling before recursively removing the current child.

Quoted source text, attributed separately from HOL analysis.