Answer in brief
CVE-2022-49560 records a High severity (CVSS 7.8) vulnerability in exfat: check if cluster num is valid. 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 7.8. 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 | >=1e49a94cf707204b66a3fb242f2814712c941f52 <82f723b8a5adf497f9e34c702a30ca7298615654 || >=1e49a94cf707204b66a3fb242f2814712c941f52 <c504167adc3248095a905fa0700a9693897cb5ed || >=1e49a94cf707204b66a3fb242f2814712c941f52 <7c58b14b6f9cde9f69e7fa053ab73f6e013a7131 || >=1e49a94cf707204b66a3fb242f2814712c941f52 <2193286402df2d9c53294f7a858d5e6fd7346e08 || >=1e49a94cf707204b66a3fb242f2814712c941f52 <64ba4b15e5c045f8b746c6da5fc9be9a6b00b61d | 82f723b8a5adf497f9e34c702a30ca7298615654, c504167adc3248095a905fa0700a9693897cb5ed, 7c58b14b6f9cde9f69e7fa053ab73f6e013a7131, 2193286402df2d9c53294f7a858d5e6fd7346e08, 64ba4b15e5c045f8b746c6da5fc9be9a6b00b61d |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Feb 26, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: exfat: check if cluster num is valid Syzbot reported slab-out-of-bounds read in exfat_clear_bitmap. This was triggered by reproducer calling truncute with size 0, which causes the following trace: BUG: KASAN: slab-out-of-bounds in exfat_clear_bitmap+0x147/0x490 fs/exfat/balloc.c:174 Read of size 8 at addr ffff888115aa9508 by task syz-executor251/365 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118 print_address_description+0x81/0x3c0 mm/kasan/report.c:233 __kasan_report mm/kasan/report.c:419 [inline] kasan_report+0x1a4/0x1f0 mm/kasan/report.c:436 __asan_report_load8_noabort+0x14/0x20 mm/kasan/report_generic.c:309 exfat_clear_bitmap+0x147/0x490 fs/exfat/balloc.c:174 exfat_free_cluster+0x25a/0x4a0 fs/exfat/fatent.c:181 __exfat_truncate+0x99e/0xe00 fs/exfat/file.c:217 exfat_truncate+0x11b/0x4f0 fs/exfat/file.c:243 exfat_setattr+0xa03/0xd40 fs/exfat/file.c:339 notify_change+0xb76/0xe10 fs/attr.c:336 do_truncate+0x1ea/0x2d0 fs/open.c:65 Move the is_valid_cluster() helper from fatent.c to a common header to make it reusable in other *.c files. And add is_valid_cluster() to validate if cluster number is within valid range in exfat_clear_bitmap() and exfat_set_bitmap().
Quoted source text, attributed separately from HOL analysis.