CVE-2022-49762
What it is
In the Linux kernel, the following vulnerability has been resolved: ntfs: check overflow when iterating ATTR_RECORDs Kernel iterates over ATTR_RECORDs in mft record in ntfs_attr_find(). Because the ATTR_RECORDs are next to each other, kernel can get the next ATTR_RECORD from end address of current ATTR_RECORD, through current ATTR_RECORD length field. The problem is that during iteration, when kernel calculates the end address of current ATTR_RECORD, kernel may trigger an integer overflow bug in executing `a = (ATTR_RECORD*)((u8*)a + le32_to_cpu(a->length))`. This may wrap, leading to a forever iteration on 32bit systems. This patch solves it by adding some checks on calculating end address of current ATTR_RECORD during iteration.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 4.9.334
- Linux Kernel < 4.14.300
- Linux Kernel < 4.19.267
- Linux Kernel < 5.4.225
- Linux Kernel < 5.10.156
- Linux Kernel < 5.15.80
- Linux Kernel < 6.0.10
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-49762.md and follow it. Check whether this project is affected by CVE-2022-49762. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/45683723f6b53e39e8a4cec0894e61fd6ec71989
- https://git.kernel.org/stable/c/5559eb5809353a83a40a1e4e7f066431c7b83020
- https://git.kernel.org/stable/c/63095f4f3af59322bea984a6ae44337439348fe0
- https://git.kernel.org/stable/c/785b2af9654b8beac55644e36da0085c5d776361
- https://git.kernel.org/stable/c/86f36de14dce5802856bb7a5921d74439db00b64
- https://git.kernel.org/stable/c/957732a09c3828267c2819d31c425aa793dd475b
- https://git.kernel.org/stable/c/b612f924f296408d7d02fb4cd01218afd4ed7184
- https://git.kernel.org/stable/c/b63ddb3ba61e2d3539f87e095c881e552bc45dab
References
- https://git.kernel.org/stable/c/45683723f6b53e39e8a4cec0894e61fd6ec71989
- https://git.kernel.org/stable/c/5559eb5809353a83a40a1e4e7f066431c7b83020
- https://git.kernel.org/stable/c/63095f4f3af59322bea984a6ae44337439348fe0
- https://git.kernel.org/stable/c/785b2af9654b8beac55644e36da0085c5d776361
- https://git.kernel.org/stable/c/86f36de14dce5802856bb7a5921d74439db00b64
- https://git.kernel.org/stable/c/957732a09c3828267c2819d31c425aa793dd475b
- https://git.kernel.org/stable/c/b612f924f296408d7d02fb4cd01218afd4ed7184
- https://git.kernel.org/stable/c/b63ddb3ba61e2d3539f87e095c881e552bc45dab