BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49352High confidence

ext4: fix warning in ext4_handle_inode_extension

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-54876

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ext4: fix warning in ext4_handle_inode_extension We got issue as follows: EXT4-fs error (device loop0) in ext4_reserve_inode_write:5741: Out of memory EXT4-fs error (device loop0): ext4_setattr:5462: inode #13: comm syz-executor.0: mark_inode_dirty error EXT4-fs error (device loop0) in ext4_setattr:5519: Out of memory EXT4-fs error (device loop0): ext4_ind_map_blocks:595: inode #13: comm syz-executor.0: Can't allocate blocks for non-extent mapped inodes with bigalloc ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4361 at fs/ext4/file.c:301 ext4_file_write_iter+0x11c9/0x1220 Modules linked in: CPU: 1 PID: 4361 Comm: syz-executor.0 Not tainted 5.10.0+ #1 RIP: 0010:ext4_file_write_iter+0x11c9/0x1220 RSP: 0018:ffff924d80b27c00 EFLAGS: 00010282 RAX: ffffffff815a3379 RBX: 0000000000000000 RCX: 000000003b000000 RDX: ffff924d81601000 RSI: 00000000000009cc RDI: 00000000000009cd RBP: 000000000000000d R08: ffffffffbc5a2c6b R09: 0000902e0e52a96f R10: ffff902e2b7c1b40 R11: ffff902e2b7c1b40 R12: 000000000000000a R13: 0000000000000001 R14: ffff902e0e52aa10 R15: ffffffffffffff8b FS: 00007f81a7f65700(0000) GS:ffff902e3bc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffff600400 CR3: 000000012db88001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: do_iter_readv_writev+0x2e5/0x360 do_iter_write+0x112/0x4c0 do_pwritev+0x1e5/0x390 __x64_sys_pwritev2+0x7e/0xa0 do_syscall_64+0x37/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Above issue may happen as follows: Assume inode.i_size=4096 EXT4_I(inode)->i_disksize=4096 step 1: set inode->i_isize = 8192 ext4_setattr if (attr->ia_size != inode->i_size) EXT4_I(inode)->i_disksize = attr->ia_size; rc = ext4_mark_inode_dirty ext4_reserve_inode_write ext4_get_inode_loc __ext4_get_inode_loc sb_getblk --> return -ENOMEM ... if (!error) ->will not update i_size i_size_write(inode, attr->ia_size); Now: inode.i_size=4096 EXT4_I(inode)->i_disksize=8192 step 2: Direct write 4096 bytes ext4_file_write_iter ext4_dio_write_iter iomap_dio_rw ->return error if (extend) ext4_handle_inode_extension WARN_ON_ONCE(i_size_read(inode) < EXT4_I(inode)->i_disksize); ->Then trigger warning. To solve above issue, if mark inode dirty failed in ext4_setattr just set 'EXT4_I(inode)->i_disksize' with old value.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: fix warning in ext4_handle_inode_extension We got issue as follows: EXT4-fs error (device loop0) in ext4_reserve_inode_write:5741: Out of memory EXT4-fs error (device loop0): ext4_setattr:5462: inode #13: comm syz-executor.0: mark_inode_dirty error EXT4-fs error (device loop0) in ext4_setattr:5519: Out of memory EXT4-fs error (device loop0): ext4_ind_map_blocks:595: inode #13: comm syz-executor.0: Can't allocate blocks for non-extent mapped inodes with bigalloc ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4361 at fs/ext4/file.c:301 ext4_file_write_iter+0x11c9/0x1220 Modules linked in: CPU: 1 PID: 4361 Comm: syz-executor.0 Not tainted 5.10.0+ #1 RIP: 0010:ext4_file_write_iter+0x11c9/0x1220 RSP: 0018:ffff924d80b27c00 EFLAGS: 00010282 RAX: ffffffff815a3379 RBX: 0000000000000000 RCX: 000000003b000000 RDX: ffff924d81601000 RSI: 00000000000009cc RDI: 00000000000009cd RBP: 000000000000000d R08: ffffffffbc5a2c6b R09: 0000902e0e52a96f R10: ffff902e2b7c1b40 R11: ffff902e2b7c1b40 R12: 000000000000000a R13: 0000000000000001 R14: ffff902e0e52aa10 R15: ffffffffffffff8b FS: 00007f81a7f65700(0000) GS:ffff902e3bc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffff600400 CR3: 000000012db88001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: do_iter_readv_writev+0x2e5/0x360 do_iter_write+0x112/0x4c0 do_pwritev+0x1e5/0x390 __x64_sys_pwritev2+0x7e/0xa0 do_syscall_64+0x37/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Above issue may happen as follows: Assume inode.i_size=4096 EXT4_I(inode)->i_disksize=4096 step 1: set inode->i_isize = 8192 ext4_setattr if (attr->ia_size != inode->i_size) EXT4_I(inode)->i_disksize = attr->ia_size; rc = ext4_mark_inode_dirty ext4_reserve_inode_write ext4_get_inode_loc __ext4_get_inode_loc sb_getblk --> return -ENOMEM ... if (!error) ->will not update i_size i_size_write(inode, attr->ia_size); Now: inode.i_size=4096 EXT4_I(inode)->i_disksize=8192 step 2: Direct write 4096 bytes ext4_file_write_iter ext4_dio_write_iter iomap_dio_rw ->return error if (extend) ext4_handle_inode_extension WARN_ON_ONCE(i_size_read(inode) < EXT4_I(inode)->i_disksize); ->Then trigger warning. To solve above issue, if mark inode dirty failed in ext4_setattr just set 'EXT4_I(inode)->i_disksize' with old value.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: fix warning in ext4_handle_inode_extension We got issue as follows: EXT4-fs error (device loop0) in ext4_reserve_inode_write:5741: Out of memory EXT4-fs error (device loop0): ext4_setattr:5462: inode #13: comm syz-executor.0: mark_inode_dirty error EXT4-fs error (device loop0) in ext4_setattr:5519: Out of memory EXT4-fs error (device loop0): ext4_ind_map_blocks:595: inode #13: comm syz-executor.0: Can't allocate blocks for non-extent mapped inodes with bigalloc ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4361 at fs/ext4/file.c:301 ext4_file_write_iter+0x11c9/0x1220 Modules linked in: CPU: 1 PID: 4361 Comm: syz-executor.0 Not tainted 5.10.0+ #1 RIP: 0010:ext4_file_write_iter+0x11c9/0x1220 RSP: 0018:ffff924d80b27c00 EFLAGS: 00010282 RAX: ffffffff815a3379 RBX: 0000000000000000 RCX: 000000003b000000 RDX: ffff924d81601000 RSI: 00000000000009cc RDI: 00000000000009cd RBP: 000000000000000d R08: ffffffffbc5a2c6b R09: 0000902e0e52a96f R10: ffff902e2b7c1b40 R11: ffff902e2b7c1b40 R12: 000000000000000a R13: 0000000000000001 R14: ffff902e0e52aa10 R15: ffffffffffffff8b FS: 00007f81a7f65700(0000) GS:ffff902e3bc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffff600400 CR3: 000000012db88001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: do_iter_readv_writev+0x2e5/0x360 do_iter_write+0x112/0x4c0 do_pwritev+0x1e5/0x390 __x64_sys_pwritev2+0x7e/0xa0 do_syscall_64+0x37/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Above issue may happen as follows: Assume inode.i_size=4096 EXT4_I(inode)->i_disksize=4096 step 1: set inode->i_isize = 8192 ext4_setattr if (attr->ia_size != inode->i_size) EXT4_I(inode)->i_disksize = attr->ia_size; rc = ext4_mark_inode_dirty ext4_reserve_inode_write ext4_get_inode_loc __ext4_get_inode_loc sb_getblk --> return -ENOMEM ... if (!error) ->will not update i_size i_size_write(inode, attr->ia_size); Now: inode.i_size=4096 EXT4_I(inode)->i_disksize=8192 step 2: Direct write 4096 bytes ext4_file_write_iter ext4_dio_write_iter iomap_dio_rw ->return error if (extend) ext4_handle_inode_extension WARN_ON_ONCE(i_size_read(inode) < EXT4_I(inode)->i_disksize); ->Then trigger warning. To solve above issue, if mark inode dirty failed in ext4_setattr just set 'EXT4_I(inode)->i_disksize' with old value.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49323 Référence CVE CVE-2022-49330 https://www.cve.org/CVERecord?id=CVE-2022-49330 Référence CVE CVE-2022-49334 https://www.cve.org/CVERecord?id=CVE-2022-49334 Référence CVE CVE-2022-49339 https://www.cve.org/CVERecord?id=CVE-2022-49339 Référence CVE CVE-2022-49340 https://www.cve.org/CVERecord?id=CVE-2022-49340 Référence CVE CVE-2022-49341 https://www.cve.org/CVERecord?id=CVE-2022-49341 Référence CVE CVE-2022-49343 https://www.cve.org/CVERecord?id=CVE-2022-49343 Référence CVE CVE-2022-49345 https://www.cve.org/CVERecord?id=CVE-2022-49345 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49353 https://www.cve.org/CVERecord?id=CVE-2022-49353 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49372 https://www.cve.org/CVERecord?id=CVE-2022-49372 Référence CVE CVE-2022-49374 https://www.cve.org/CVERecord?id=CVE-2022-49374 Référence CVE CVE-2022-49376 https://www.cve.org/CVERecord?id=CVE-2022-49376 Référence CVE CVE-2022-49378 https://www.cve.org/CVERecord?id=CVE-2022-49378 Référence CVE CVE-2022-49379 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49343 Référence CVE CVE-2022-49344 https://www.cve.org/CVERecord?id=CVE-2022-49344 Référence CVE CVE-2022-49345 https://www.cve.org/CVERecord?id=CVE-2022-49345 Référence CVE CVE-2022-49346 https://www.cve.org/CVERecord?id=CVE-2022-49346 Référence CVE CVE-2022-49347 https://www.cve.org/CVERecord?id=CVE-2022-49347 Référence CVE CVE-2022-49348 https://www.cve.org/CVERecord?id=CVE-2022-49348 Référence CVE CVE-2022-49349 https://www.cve.org/CVERecord?id=CVE-2022-49349 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49353 https://www.cve.org/CVERecord?id=CVE-2022-49353 Référence CVE CVE-2022-49354 https://www.cve.org/CVERecord?id=CVE-2022-49354 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49359 https://www.cve.org/CVERecord?id=CVE-2022-49359 Référence CVE CVE-2022-49362 https://www.cve.org/CVERecord?id=CVE-2022-49362 Référence CVE CVE-2022-49365 https://www.cve.org/CVERecord?id=CVE-2022-49365 Référence CVE CVE-2022-49367 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49342 Référence CVE CVE-2022-49343 https://www.cve.org/CVERecord?id=CVE-2022-49343 Référence CVE CVE-2022-49345 https://www.cve.org/CVERecord?id=CVE-2022-49345 Référence CVE CVE-2022-49346 https://www.cve.org/CVERecord?id=CVE-2022-49346 Référence CVE CVE-2022-49347 https://www.cve.org/CVERecord?id=CVE-2022-49347 Référence CVE CVE-2022-49348 https://www.cve.org/CVERecord?id=CVE-2022-49348 Référence CVE CVE-2022-49349 https://www.cve.org/CVERecord?id=CVE-2022-49349 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49353 https://www.cve.org/CVERecord?id=CVE-2022-49353 Référence CVE CVE-2022-49354 https://www.cve.org/CVERecord?id=CVE-2022-49354 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49359 https://www.cve.org/CVERecord?id=CVE-2022-49359 Référence CVE CVE-2022-49362 https://www.cve.org/CVERecord?id=CVE-2022-49362 Référence CVE CVE-2022-49365 https://www.cve.org/CVERecord?id=CVE-2022-49365 Référence CVE CVE-2022-49367 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49342 Référence CVE CVE-2022-49343 https://www.cve.org/CVERecord?id=CVE-2022-49343 Référence CVE CVE-2022-49345 https://www.cve.org/CVERecord?id=CVE-2022-49345 Référence CVE CVE-2022-49346 https://www.cve.org/CVERecord?id=CVE-2022-49346 Référence CVE CVE-2022-49347 https://www.cve.org/CVERecord?id=CVE-2022-49347 Référence CVE CVE-2022-49348 https://www.cve.org/CVERecord?id=CVE-2022-49348 Référence CVE CVE-2022-49349 https://www.cve.org/CVERecord?id=CVE-2022-49349 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49354 https://www.cve.org/CVERecord?id=CVE-2022-49354 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49367 https://www.cve.org/CVERecord?id=CVE-2022-49367 Référence CVE CVE-2022-49368 https://www.cve.org/CVERecord?id=CVE-2022-49368 Référence CVE CVE-2022-49370 https://www.cve.org/CVERecord?id=CVE-2022-49370 Référence CVE CVE-2022-49371 https://www.cve.org/CVERecord?id=CVE-2022-49371 Référence CVE CVE-2022-49373 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 < adf490083ca52ebfb0b2fe64ff1ead00c0452dd7; b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 < b81d2ff6885e38fc745eeaf9565775055778fc0b; b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 < e383c2aa5f02ab571530dc5c5696479672478c25; b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 < 1bcce88da60eccc946c0f4ed942b0f08cd565778; b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 < f4534c9fc94d22383f187b9409abb3f9df2e3db3; 5.5
Fixed
< 5.5; 5.10.121 ≤ 5.10.*; 5.15.46 ≤ 5.15.*; 5.17.14 ≤ 5.17.*; 5.18.3 ≤ 5.18.*; 5.19 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 11 May 2026, 18:58 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-54876
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-54876↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49352 · cve.blacktree.nl