Answer in brief
CVE-2025-21853 records a Medium severity (CVSS 5.5) vulnerability in bpf: avoid holding freeze_mutex during mmap operation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. 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-21853 records a Medium severity (CVSS 5.5) vulnerability in bpf: avoid holding freeze_mutex during mmap operation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. 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), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fc9702273e2edb90400a34b3be76f7b08fa3344b <2ce31c97c219b4fe797749f950274f246eb88c49 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <4759acbd44d24a69b7b14848012ec4201d6c5501 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <29cfda62ab4d92ab94123813db49ab76c1e61b29 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <271e49f8a58edba65bc2b1250a0abaa98c4bfdbe || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <bc27c52eea189e8f7492d40739b7746d67b65beb | 2ce31c97c219b4fe797749f950274f246eb88c49, 0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f, 4759acbd44d24a69b7b14848012ec4201d6c5501, 29cfda62ab4d92ab94123813db49ab76c1e61b29, d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4, 271e49f8a58edba65bc2b1250a0abaa98c4bfdbe, bc27c52eea189e8f7492d40739b7746d67b65beb |
| Linux/Linuxgeneric | 5.5 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Mar 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/[email protected]/
Quoted source text, attributed separately from HOL analysis.
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), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fc9702273e2edb90400a34b3be76f7b08fa3344b <2ce31c97c219b4fe797749f950274f246eb88c49 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <4759acbd44d24a69b7b14848012ec4201d6c5501 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <29cfda62ab4d92ab94123813db49ab76c1e61b29 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4 || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <271e49f8a58edba65bc2b1250a0abaa98c4bfdbe || >=fc9702273e2edb90400a34b3be76f7b08fa3344b <bc27c52eea189e8f7492d40739b7746d67b65beb | 2ce31c97c219b4fe797749f950274f246eb88c49, 0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f, 4759acbd44d24a69b7b14848012ec4201d6c5501, 29cfda62ab4d92ab94123813db49ab76c1e61b29, d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4, 271e49f8a58edba65bc2b1250a0abaa98c4bfdbe, bc27c52eea189e8f7492d40739b7746d67b65beb |
| Linux/Linuxgeneric | 5.5 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Mar 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/[email protected]/
Quoted source text, attributed separately from HOL analysis.