If a malicious daemon sends a non-NUL-terminated list, the fusefs kernel module may read beyond the end of one heap-allocated buffer and potentially write beyond the end of a second buffer. A malicious daemon could disclose up to 253 bytes of kernel heap memory, or it could inject up to 250 attacker-controlled bytes into unallocated kernel heap space.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 21 May 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 21 May 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freebsd
Freebsd freebsd |
|
| Vendors & Products |
Freebsd
Freebsd freebsd |
Thu, 21 May 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Thu, 21 May 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When a fusefs file system implements extended attributes, the kernel may send a FUSE_LISTXATTR message to the userspace daemon to retrieve the list of extended attributes for a given file. The FUSE protocol requires the daemon to return a packed list of NUL-terminated strings. The fusefs kernel module calls strlen() on this daemon-supplied buffer without first verifying that the entire list is NUL-terminated. If a malicious daemon sends a non-NUL-terminated list, the fusefs kernel module may read beyond the end of one heap-allocated buffer and potentially write beyond the end of a second buffer. A malicious daemon could disclose up to 253 bytes of kernel heap memory, or it could inject up to 250 attacker-controlled bytes into unallocated kernel heap space. | |
| Title | Heap overflow in FUSE_LISTXATTR | |
| Weaknesses | CWE-122 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: freebsd
Published:
Updated: 2026-05-21T13:47:03.794Z
Reserved: 2026-05-11T16:27:44.891Z
Link: CVE-2026-45252
Updated: 2026-05-21T12:29:37.010Z
Status : Undergoing Analysis
Published: 2026-05-21T10:16:26.157
Modified: 2026-05-21T15:16:27.807
Link: CVE-2026-45252
No data.
OpenCVE Enrichment
Updated: 2026-05-21T16:30:14Z