Answer in brief
CVE-2025-21811 records a Unknown severity vulnerability in nilfs2: protect access to buffers with no active references. 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.
Answer in brief
CVE-2025-21811 records a Unknown severity vulnerability in nilfs2: protect access to buffers with no active references. 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 | >=8c26c4e2694a163d525976e804d81cd955bbb40c <e1fc4a90a90ea8514246c45435662531975937d9 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <72cf688d0ce7e642b12ddc9b2a42524737ec1b4a || >=8c26c4e2694a163d525976e804d81cd955bbb40c <d8ff250e085a4c4cdda4ad1cdd234ed110393143 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <58c27fa7a610b6e8d44e6220e7dbddfbaccaf439 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <8e1b9201c9a24638cf09c6e1c9f224157328010b || >=8c26c4e2694a163d525976e804d81cd955bbb40c <4b08d23d7d1917bef4fbee8ad81372f49b006656 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <c437dfac9f7a5a46ac2a5e6d6acd3059e9f68188 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <367a9bffabe08c04f6d725032cce3d891b2b9e1a | e1fc4a90a90ea8514246c45435662531975937d9, 72cf688d0ce7e642b12ddc9b2a42524737ec1b4a, d8ff250e085a4c4cdda4ad1cdd234ed110393143, 58c27fa7a610b6e8d44e6220e7dbddfbaccaf439, 8e1b9201c9a24638cf09c6e1c9f224157328010b, 4b08d23d7d1917bef4fbee8ad81372f49b006656, c437dfac9f7a5a46ac2a5e6d6acd3059e9f68188, 367a9bffabe08c04f6d725032cce3d891b2b9e1a |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
Feb 27, 2025
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: nilfs2: protect access to buffers with no active references nilfs_lookup_dirty_data_buffers(), which iterates through the buffers attached to dirty data folios/pages, accesses the attached buffers without locking the folios/pages. For data cache, nilfs_clear_folio_dirty() may be called asynchronously when the file system degenerates to read only, so nilfs_lookup_dirty_data_buffers() still has the potential to cause use after free issues when buffers lose the protection of their dirty state midway due to this asynchronous clearing and are unintentionally freed by try_to_free_buffers(). Eliminate this race issue by adjusting the lock section in this function.
Quoted source text, attributed separately from HOL analysis.
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 | >=8c26c4e2694a163d525976e804d81cd955bbb40c <e1fc4a90a90ea8514246c45435662531975937d9 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <72cf688d0ce7e642b12ddc9b2a42524737ec1b4a || >=8c26c4e2694a163d525976e804d81cd955bbb40c <d8ff250e085a4c4cdda4ad1cdd234ed110393143 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <58c27fa7a610b6e8d44e6220e7dbddfbaccaf439 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <8e1b9201c9a24638cf09c6e1c9f224157328010b || >=8c26c4e2694a163d525976e804d81cd955bbb40c <4b08d23d7d1917bef4fbee8ad81372f49b006656 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <c437dfac9f7a5a46ac2a5e6d6acd3059e9f68188 || >=8c26c4e2694a163d525976e804d81cd955bbb40c <367a9bffabe08c04f6d725032cce3d891b2b9e1a | e1fc4a90a90ea8514246c45435662531975937d9, 72cf688d0ce7e642b12ddc9b2a42524737ec1b4a, d8ff250e085a4c4cdda4ad1cdd234ed110393143, 58c27fa7a610b6e8d44e6220e7dbddfbaccaf439, 8e1b9201c9a24638cf09c6e1c9f224157328010b, 4b08d23d7d1917bef4fbee8ad81372f49b006656, c437dfac9f7a5a46ac2a5e6d6acd3059e9f68188, 367a9bffabe08c04f6d725032cce3d891b2b9e1a |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
Feb 27, 2025
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: nilfs2: protect access to buffers with no active references nilfs_lookup_dirty_data_buffers(), which iterates through the buffers attached to dirty data folios/pages, accesses the attached buffers without locking the folios/pages. For data cache, nilfs_clear_folio_dirty() may be called asynchronously when the file system degenerates to read only, so nilfs_lookup_dirty_data_buffers() still has the potential to cause use after free issues when buffers lose the protection of their dirty state midway due to this asynchronous clearing and are unintentionally freed by try_to_free_buffers(). Eliminate this race issue by adjusting the lock section in this function.
Quoted source text, attributed separately from HOL analysis.