CVE-2022-49560
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-49560
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-49560.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2022-49560
- Downstream
- Related
- Published
- 2025-02-26T02:14:05Z
- Modified
- 2025-10-15T23:32:20.191287Z
- Severity
-
- 7.1 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H CVSS Calculator
- Summary
- exfat: check if cluster num is valid
- Details
-
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 exfatclearbitmap. This was triggered by reproducer calling truncute with size 0, which causes the following trace:
BUG: KASAN: slab-out-of-bounds in exfatclearbitmap+0x147/0x490 fs/exfat/balloc.c:174 Read of size 8 at addr ffff888115aa9508 by task syz-executor251/365
Call Trace: _dumpstack lib/dumpstack.c:77 [inline] dumpstacklvl+0x1e2/0x24b lib/dumpstack.c:118 printaddressdescription+0x81/0x3c0 mm/kasan/report.c:233 _kasanreport mm/kasan/report.c:419 [inline] kasanreport+0x1a4/0x1f0 mm/kasan/report.c:436 _asanreportload8noabort+0x14/0x20 mm/kasan/reportgeneric.c:309 exfatclearbitmap+0x147/0x490 fs/exfat/balloc.c:174 exfatfreecluster+0x25a/0x4a0 fs/exfat/fatent.c:181 _exfattruncate+0x99e/0xe00 fs/exfat/file.c:217 exfattruncate+0x11b/0x4f0 fs/exfat/file.c:243 exfatsetattr+0xa03/0xd40 fs/exfat/file.c:339 notifychange+0xb76/0xe10 fs/attr.c:336 dotruncate+0x1ea/0x2d0 fs/open.c:65
Move the isvalidcluster() helper from fatent.c to a common header to make it reusable in other *.c files. And add isvalidcluster() to validate if cluster number is within valid range in exfatclearbitmap() and exfatsetbitmap().
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/2193286402df2d9c53294f7a858d5e6fd7346e08
- https://git.kernel.org/stable/c/64ba4b15e5c045f8b746c6da5fc9be9a6b00b61d
- https://git.kernel.org/stable/c/7c58b14b6f9cde9f69e7fa053ab73f6e013a7131
- https://git.kernel.org/stable/c/82f723b8a5adf497f9e34c702a30ca7298615654
- https://git.kernel.org/stable/c/c504167adc3248095a905fa0700a9693897cb5ed
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1e49a94cf707204b66a3fb242f2814712c941f52Fixed82f723b8a5adf497f9e34c702a30ca7298615654
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1e49a94cf707204b66a3fb242f2814712c941f52Fixedc504167adc3248095a905fa0700a9693897cb5ed
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1e49a94cf707204b66a3fb242f2814712c941f52Fixed7c58b14b6f9cde9f69e7fa053ab73f6e013a7131
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1e49a94cf707204b66a3fb242f2814712c941f52Fixed2193286402df2d9c53294f7a858d5e6fd7346e08
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1e49a94cf707204b66a3fb242f2814712c941f52Fixed64ba4b15e5c045f8b746c6da5fc9be9a6b00b61d