Answer in brief
CVE-2022-50367 records a Unknown severity vulnerability in fs: fix UAF/GPF bug in nilfs_mdt_destroy. 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-2022-50367 records a Unknown severity vulnerability in fs: fix UAF/GPF bug in nilfs_mdt_destroy. 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 | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d1ff475d7c83289d0a7faef346ea3bbf90818bad || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c0aa76b0f17f59dd9c9d3463550a2986a1d592e4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70e4f70d54e0225f91814e8610477d65f33cefe4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1e555c3ed1fce4b278aaebe18a64a934cece57d8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64b79e632869ad3ef6c098a4731d559381da1115 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <81de80330fa6907aec32eb54c5619059e6e36452 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a96b532098284ecf8e4849b8b9e5fc7a28bdee9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2e488f13755ffbb60f307e991b27024716a33b29 | d1ff475d7c83289d0a7faef346ea3bbf90818bad, c0aa76b0f17f59dd9c9d3463550a2986a1d592e4, ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48, 70e4f70d54e0225f91814e8610477d65f33cefe4, 1e555c3ed1fce4b278aaebe18a64a934cece57d8, 64b79e632869ad3ef6c098a4731d559381da1115, 81de80330fa6907aec32eb54c5619059e6e36452, 2a96b532098284ecf8e4849b8b9e5fc7a28bdee9, 2e488f13755ffbb60f307e991b27024716a33b29 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Sep 17, 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: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)
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 | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d1ff475d7c83289d0a7faef346ea3bbf90818bad || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c0aa76b0f17f59dd9c9d3463550a2986a1d592e4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70e4f70d54e0225f91814e8610477d65f33cefe4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1e555c3ed1fce4b278aaebe18a64a934cece57d8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64b79e632869ad3ef6c098a4731d559381da1115 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <81de80330fa6907aec32eb54c5619059e6e36452 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a96b532098284ecf8e4849b8b9e5fc7a28bdee9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2e488f13755ffbb60f307e991b27024716a33b29 | d1ff475d7c83289d0a7faef346ea3bbf90818bad, c0aa76b0f17f59dd9c9d3463550a2986a1d592e4, ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48, 70e4f70d54e0225f91814e8610477d65f33cefe4, 1e555c3ed1fce4b278aaebe18a64a934cece57d8, 64b79e632869ad3ef6c098a4731d559381da1115, 81de80330fa6907aec32eb54c5619059e6e36452, 2a96b532098284ecf8e4849b8b9e5fc7a28bdee9, 2e488f13755ffbb60f307e991b27024716a33b29 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Sep 17, 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: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)
Quoted source text, attributed separately from HOL analysis.