CVE-2022-49166 json
ntfs: add sanity check on allocation size
published 2025-02-26 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-55059
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ntfs: add sanity check on allocation size
ntfs_read_inode_mount invokes ntfs_malloc_nofs with zero allocation size. It triggers one BUG in the __ntfs_malloc function.
Fix this by adding sanity check on ni->attr_list_size.
Patch / fix
- Linux Linux 4.9.311, 4.14.276, 4.19.238, 5.4.189, 5.10.110, 5.15.33, 5.16.19, 5.17.2, 5.18
- linux Debian 14, Debian 13, Debian 12 5.17.3-1
debian advisories DEBIAN-CVE-2022-49166
- linux Ubuntu 18.04 LTS 4.15.0-189.200
- linux Ubuntu 20.04 LTS 5.4.0-117.132
- linux Ubuntu 22.04 LTS 5.15.0-37.39
- linux-aws Ubuntu 18.04 LTS 4.15.0-1137.148
- linux-aws Ubuntu 20.04 LTS 5.4.0-1078.84
- linux-aws Ubuntu 22.04 LTS 5.15.0-1011.14
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1078.84
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1008.12
ubuntu advisories UBUNTU-CVE-2022-49166
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/bd8d7daa0e53b184a2f3c6e0d47330780d0a0650 commit
- git.kernel.org/stable/c/21d490232f323ed4053eb9924615e6fea291f154 commit
- git.kernel.org/stable/c/07793d2e55563124108762f4e5f811db92ffe02f commit
- git.kernel.org/stable/c/fe41ad8be036a3de3e4bdde709551aeb4de2fe7d commit
- git.kernel.org/stable/c/b230f2d9441a34c7f483d39ab78519bcf73cc2e0 commit
- git.kernel.org/stable/c/24ab2d4ef52c2dbb62a60844b87fc8872383407a commit
- git.kernel.org/stable/c/115fae2c1566eacc5ad2055f72521354612e72c3 commit
- git.kernel.org/stable/c/c641087d381a08363e5f14179bc6b0a23eca7c47 commit
- git.kernel.org/stable/c/714fbf2647b1a33d914edd695d4da92029c7e7c0 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49166 updated
kernel: ntfs: add sanity check on allocation size
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/bd8d7daa0e53b184a2f3c6e0d47330780d0a0650
patch
-
git.kernel.org
/stable/c/21d490232f323ed4053eb9924615e6fea291f154
patch
-
git.kernel.org
/stable/c/07793d2e55563124108762f4e5f811db92ffe02f
patch
-
git.kernel.org
/stable/c/fe41ad8be036a3de3e4bdde709551aeb4de2fe7d
patch
-
git.kernel.org
/stable/c/b230f2d9441a34c7f483d39ab78519bcf73cc2e0
patch
-
git.kernel.org
/stable/c/24ab2d4ef52c2dbb62a60844b87fc8872383407a
patch
-
git.kernel.org
/stable/c/115fae2c1566eacc5ad2055f72521354612e72c3
patch
-
git.kernel.org
/stable/c/c641087d381a08363e5f14179bc6b0a23eca7c47
patch
-
git.kernel.org
/stable/c/714fbf2647b1a33d914edd695d4da92029c7e7c0
patch
Sources
- CVE List CVE-2022-49166
- NVD CVE-2022-49166
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.