Bug 2363482 (CVE-2022-49762) - CVE-2022-49762 kernel: ntfs: check overflow when iterating ATTR_RECORDs
Summary: CVE-2022-49762 kernel: ntfs: check overflow when iterating ATTR_RECORDs
Keywords:
Status: NEW
Alias: CVE-2022-49762
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-01 15:06 UTC by OSIDB Bzimport
Modified: 2025-05-02 04:41 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-01 15:06:30 UTC
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.

Comment 1 Avinash Hanwate 2025-05-02 04:30:29 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050112-CVE-2022-49762-216f@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.