Answer in brief
CVE-2022-50334 records a Medium severity (CVSS 5.5) vulnerability in hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param(). 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=32021982a324dce93b4ae00c06213bf45fb319c8 <fa71639873518e3587632ae58e25e4a96b57fa90 || >=32021982a324dce93b4ae00c06213bf45fb319c8 <dcd28191be9bbf307ba51a5b485773a55b0037c4 || >=32021982a324dce93b4ae00c06213bf45fb319c8 <9a8862820cbf1f18dca4f3b4c289d88561b3a384 || >=32021982a324dce93b4ae00c06213bf45fb319c8 <965e8f8ae0f642b5528f5a82b7bcaf15a659d5bd || >=32021982a324dce93b4ae00c06213bf45fb319c8 <f2207145693ae5697a7b59e2add4b92f9e5b0e3c || >=32021982a324dce93b4ae00c06213bf45fb319c8 <26215b7ee923b9251f7bb12c4e5f09dc465d35f2 | fa71639873518e3587632ae58e25e4a96b57fa90, dcd28191be9bbf307ba51a5b485773a55b0037c4, 9a8862820cbf1f18dca4f3b4c289d88561b3a384, 965e8f8ae0f642b5528f5a82b7bcaf15a659d5bd, f2207145693ae5697a7b59e2add4b92f9e5b0e3c, 26215b7ee923b9251f7bb12c4e5f09dc465d35f2 |
| Linux/Linuxgeneric | 5.1 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows: ====================================================== KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380 [...] Call Trace: <TASK> vfs_parse_fs_param fs/fs_context.c:148 [inline] vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191 generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231 do_new_mount fs/namespace.c:3036 [inline] path_mount+0x12de/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] </TASK> ====================================================== According to commit "vfs: parse: deal with zero length string value", kernel will set the param->string to null pointer in vfs_parse_fs_string() if fs string has zero length. Yet the problem is that, hugetlbfs_parse_param() will dereference the param->string, without checking whether it is a null pointer. To be more specific, if hugetlbfs_parse_param() parses an illegal mount parameter, such as "size=,", kernel will constructs struct fs_parameter with null pointer in vfs_parse_fs_string(), then passes this struct fs_parameter to hugetlbfs_parse_param(), which triggers the above null-ptr-deref bug. This patch solves it by adding sanity check on param->string in hugetlbfs_parse_param().
Quoted source text, attributed separately from HOL analysis.