Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 28 Mar 2026 03:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libfuse Project
Libfuse Project libfuse |
|
| CPEs | cpe:2.3:a:libfuse_project:libfuse:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Libfuse Project
Libfuse Project libfuse |
Thu, 26 Mar 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Wed, 25 Mar 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 23 Mar 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libfuse
Libfuse libfuse |
|
| Vendors & Products |
Libfuse
Libfuse libfuse |
Fri, 20 Mar 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | libfuse is the reference implementation of the Linux FUSE. From version 3.18.0 to before version 3.18.2, a NULL pointer dereference and memory leak in fuse_uring_init_queue allows a local user to crash the FUSE daemon or cause resource exhaustion. When numa_alloc_local fails during io_uring queue entry setup, the code proceeds with NULL pointers. When fuse_uring_register_queue fails, NUMA allocations are leaked and the function incorrectly returns success. Only the io_uring transport is affected; the traditional /dev/fuse path is not affected. PoC confirmed with AddressSanitizer/LeakSanitizer. This issue has been patched in version 3.18.2. | |
| Title | libfuse: NULL Pointer Dereference and Memory Leak in io_uring Queue Initialization | |
| Weaknesses | CWE-476 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-25T13:55:45.971Z
Reserved: 2026-03-17T22:16:36.720Z
Link: CVE-2026-33179
Updated: 2026-03-25T13:55:42.459Z
Status : Analyzed
Published: 2026-03-20T21:17:16.593
Modified: 2026-03-27T21:20:47.880
Link: CVE-2026-33179
OpenCVE Enrichment
Updated: 2026-03-29T20:28:53Z