Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49762

ntfs: check overflow when iterating ATTR_RECORDs

Medium5.5EPSS 0.22%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 35 days later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49762, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5559eb5809353a83a40a1e4e7f066431c7b83020
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 86f36de14dce5802856bb7a5921d74439db00b64
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 45683723f6b53e39e8a4cec0894e61fd6ec71989
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b612f924f296408d7d02fb4cd01218afd4ed7184
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 957732a09c3828267c2819d31c425aa793dd475b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b63ddb3ba61e2d3539f87e095c881e552bc45dab
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 785b2af9654b8beac55644e36da0085c5d776361
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 63095f4f3af59322bea984a6ae44337439348fe0
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.9.334 – ≤ 4.9.*
    • unaffected 4.14.300 – ≤ 4.14.*
    • unaffected 4.19.267 – ≤ 4.19.*
    • unaffected 5.4.225 – ≤ 5.4.*
    • unaffected 5.10.156 – ≤ 5.10.*
    • unaffected 5.15.80 – ≤ 5.15.*
    • unaffected 6.0.10 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49762 badge
[![CVE-2022-49762](https://trackcve.app/badge/CVE-2022-49762.svg)](https://trackcve.app/cve/CVE-2022-49762)

Record last updated .