NVD / CVE Program· CNA Linux

CVE-2022-49763: ntfs: fix use-after-free in ntfs_attr_find()

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 266bd5306286316758e6246ea0345133427b0f62, 4863f815463034f588a035cfd99cdca97a4f1069, 5330c423b86263ac7883fef0260b9e2229cb531e.

Low priority for now. Upgrade to Linux Linux 266bd5306286316758e6246ea0345133427b0f62, 4863f815463034f588a035cfd99cdca97a4f1069, 5330c423b86263ac7883fef0260b9e2229cb531e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix use-after-free in ntfs_attr_find() Patch series "ntfs: fix bugs about Attribute", v2. This patchset fixes three bugs relative to Attribute in record: Patch 1 adds a sanity check to ensure that, attrs_offset field in first mft record loading from disk is within bounds. Patch 2 moves the ATTR_RECORD's bounds checking earlier, to avoid dereferencing ATTR_RECORD before checking this ATTR_RECORD is within bounds. Patch 3 adds an overflow checking to avoid possible forever loop in ntfs_attr_find(). Without patch 1 and patch 2, the kernel triggersa KASAN use-after-free detection as reported by Syzkaller. Although one of patch 1 or patch 2 can fix this, we still need both of them. Because patch 1 fixes the root cause, and patch 2 not only fixes the direct cause, but also fixes the potential out-of-bounds bug. This patch (of 3): Syzkaller reported use-after-free read as follows: ================================================================== BUG: KASAN: use-after-free in ntfs_attr_find+0xc02/0xce0 fs/ntfs/attrib.c:597 Read of size 2 at addr ffff88807e352009 by task syz-executor153/3607 [...] Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x719 mm/kasan/report.c:433 kasan_report+0xb1/0x1e0 mm/kasan/report.c:495 ntfs_attr_find+0xc02/0xce0 fs/ntfs/attrib.c:597 ntfs_attr_lookup+0x1056/0x2070 fs/ntfs/attrib.c:1193 ntfs_read_inode_mount+0x89a/0x2580 fs/ntfs/inode.c:1845 ntfs_fill_super+0x1799/0x9320 fs/ntfs/super.c:2854 mount_bdev+0x34d/0x410 fs/super.c:1400 legacy_get_tree+0x105/0x220 fs/fs_context.c:610 vfs_get_tree+0x89/0x2f0 fs/super.c:1530 do_new_mount fs/namespace.c:3040 [inline] path_mount+0x1326/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] </TASK> The buggy address belongs to the physical page: page:ffffea0001f8d400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7e350 head:ffffea0001f8d400 order:3 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 0000000000000000 dead000000000122 ffff888011842140 raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88807e351f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88807e351f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88807e352000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff88807e352080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88807e352100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Kernel will loads $MFT/$DATA's first mft record in ntfs_read_inode_mount(). Yet the problem is that after loading, kernel doesn't check whether attrs_offset field is a valid value. To be more specific, if attrs_offset field is larger than bytes_allocated field, then it may trigger the out-of-bounds read bug(reported as use-after-free bug) in ntfs_attr_find(), when kernel tries to access the corresponding mft record's attribute. This patch solves it by adding the sanity check between attrs_offset field and bytes_allocated field, after loading the first mft record.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: May 1, 2025
Updated: Aug 5, 2026
EPSS: 0.2% · 12th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

ProductVersion

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernelbefore 4.9.334
linux linux kernel4.10 and later · before 4.14.300
linux linux kernel4.15 and later · before 4.19.267
linux linux kernel4.20 and later · before 5.4.225
linux linux kernel5.5 and later · before 5.10.156
linux linux kernel5.11 and later · before 5.15.80
linux linux kernel5.16 and later · before 6.0.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 79f3ac7dcd12c05b7539239a4c6fa229a50d786caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fb2004bafd1932e08d21ca604ee5844f2b7f212daffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d0006d739738a658a9c29b438444259d9f71dfa0affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 266bd5306286316758e6246ea0345133427b0f62affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b825bfbbaafbe8da2037e3a778ad660c59f9e054affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5330c423b86263ac7883fef0260b9e2229cb531eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4863f815463034f588a035cfd99cdca97a4f1069affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d85a1bec8e8d552ab13163ca1874dcd82f3d1550affected · git
- before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.0.10-1	6.0.10-1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	kernel-64kb	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	kernel-docs	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	kernel-obs-build	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	kernel-syms	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1
SUSE:Linux Enterprise Live Patching 15 SP5	kernel-livepatch-SLE15-SP5_Update_27	before 1-150500.11.7.1	1-150500.11.7.1
SUSE:Linux Enterprise Micro 5.5	kernel-default	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1
SUSE:Linux Enterprise Micro 5.5	kernel-default-base	before 5.14.21-150500.55.110.1.150500.6.51.3	5.14.21-150500.55.110.1.150500.6.51.3
SUSE:Linux Enterprise Micro 5.5	kernel-rt	before 5.14.21-150500.13.97.1	5.14.21-150500.13.97.1
SUSE:Linux Enterprise Micro 5.5	kernel-source	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1
SUSE:Linux Enterprise Micro 5.5	kernel-source-rt	before 5.14.21-150500.13.97.1	5.14.21-150500.13.97.1
SUSE:Linux Enterprise Server 15 SP5-LTSS	kernel-zfcpdump	before 5.14.21-150500.55.110.1	5.14.21-150500.55.110.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2020-36790May 1, 2025 · nvmet: fix a memory leak
22Monitor
← EarlierCVE-2022-49762May 1, 2025 · ntfs: check overflow when iterating ATTR_RECORDs
22Monitor
Later →CVE-2022-49765May 1, 2025 · net/9p: use a dedicated spinlock for trans_fd
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	266bd5306286316758e6246ea0345133427b0f62	Vendor (CNA)
Linux Linux	4863f815463034f588a035cfd99cdca97a4f1069	Vendor (CNA)
Linux Linux	5330c423b86263ac7883fef0260b9e2229cb531e	Vendor (CNA)
Linux Linux	79f3ac7dcd12c05b7539239a4c6fa229a50d786c	Vendor (CNA)
Linux Linux	b825bfbbaafbe8da2037e3a778ad660c59f9e054	Vendor (CNA)
Linux Linux	d0006d739738a658a9c29b438444259d9f71dfa0	Vendor (CNA)
Linux Linux	d85a1bec8e8d552ab13163ca1874dcd82f3d1550	Vendor (CNA)
Linux Linux	fb2004bafd1932e08d21ca604ee5844f2b7f212d	Vendor (CNA)
debian:linux	6.0.10-1 · Debian:12	Package registry (OSV)
suse:kernel-64kb	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	Package registry (OSV)
suse:kernel-default	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:kernel-default-base	5.14.21-150500.55.110.1.150500.6.51.3 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:kernel-docs	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5_Update_27	1-150500.11.7.1 · SUSE:Linux Enterprise Live Patching 15 SP5	Package registry (OSV)
suse:kernel-obs-build	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	Package registry (OSV)
suse:kernel-rt	5.14.21-150500.13.97.1 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:kernel-source	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:kernel-source-rt	5.14.21-150500.13.97.1 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:kernel-syms	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS	Package registry (OSV)
suse:kernel-zfcpdump	5.14.21-150500.55.110.1 · SUSE:Linux Enterprise Server 15 SP5-LTSS	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/266bd5306286316758e6246ea0345133427b0f62

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records