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

ceph: drop messages from MDS when unmounting

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.

2 package states
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-azure-fdeAffected, 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 4 Sept 2026
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 4 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-51323

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: ceph: drop messages from MDS when unmounting When unmounting all the dirty buffers will be flushed and after the last osd request is finished the last reference of the i_count will be released. Then it will flush the dirty cap/snap to MDSs, and the unmounting won't wait the possible acks, which will ihold the inodes when updating the metadata locally but makes no sense any more, of this. This will make the evict_inodes() to skip these inodes. If encrypt is enabled the kernel generate a warning when removing the encrypt keys when the skipped inodes still hold the keyring: WARNING: CPU: 4 PID: 168846 at fs/crypto/keyring.c:242 fscrypt_destroy_keyring+0x7e/0xd0 CPU: 4 PID: 168846 Comm: umount Tainted: G S 6.1.0-rc5-ceph-g72ead199864c #1 Hardware name: Supermicro SYS-5018R-WR/X10SRW-F, BIOS 2.0 12/17/2015 RIP: 0010:fscrypt_destroy_keyring+0x7e/0xd0 RSP: 0018:ffffc9000b277e28 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff88810d52ac00 RCX: ffff88810b56aa00 RDX: 0000000080000000 RSI: ffffffff822f3a09 RDI: ffff888108f59000 RBP: ffff8881d394fb88 R08: 0000000000000028 R09: 0000000000000000 R10: 0000000000000001 R11: 11ff4fe6834fcd91 R12: ffff8881d394fc40 R13: ffff888108f59000 R14: ffff8881d394f800 R15: 0000000000000000 FS: 00007fd83f6f1080(0000) GS:ffff88885fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f918d417000 CR3: 000000017f89a005 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> generic_shutdown_super+0x47/0x120 kill_anon_super+0x14/0x30 ceph_kill_sb+0x36/0x90 [ceph] deactivate_locked_super+0x29/0x60 cleanup_mnt+0xb8/0x140 task_work_run+0x67/0xb0 exit_to_user_mode_prepare+0x23d/0x240 syscall_exit_to_user_mode+0x25/0x60 do_syscall_64+0x40/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fd83dc39e9b Later the kernel will crash when iput() the inodes and dereferencing the "sb->s_master_keys", which has been released by the generic_shutdown_super().

What

In the Linux kernel, the following vulnerability has been resolved: ceph: drop messages from MDS when unmounting When unmounting all the dirty buffers will be flushed and after the last osd request is finished the last reference of the i_count will be released. Then it will flush the dirty cap/snap to MDSs, and the unmounting won't wait the possible acks, which will ihold the inodes when updating the metadata locally but makes no sense any more, of this. This will make the evict_inodes() to skip these inodes. If encrypt is enabled the kernel generate a warning when removing the encrypt keys when the skipped inodes still hold the keyring: WARNING: CPU: 4 PID: 168846 at fs/crypto/keyring.c:242 fscrypt_destroy_keyring+0x7e/0xd0 CPU: 4 PID: 168846 Comm: umount Tainted: G S 6.1.0-rc5-ceph-g72ead199864c #1 Hardware name: Supermicro SYS-5018R-WR/X10SRW-F, BIOS 2.0 12/17/2015 RIP: 0010:fscrypt_destroy_keyring+0x7e/0xd0 RSP: 0018:ffffc9000b277e28 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff88810d52ac00 RCX: ffff88810b56aa00 RDX: 0000000080000000 RSI: ffffffff822f3a09 RDI: ffff888108f59000 RBP: ffff8881d394fb88 R08: 0000000000000028 R09: 0000000000000000 R10: 0000000000000001 R11: 11ff4fe6834fcd91 R12: ffff8881d394fc40 R13: ffff888108f59000 R14: ffff8881d394f800 R15: 0000000000000000 FS: 00007fd83f6f1080(0000) GS:ffff88885fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f918d417000 CR3: 000000017f89a005 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> generic_shutdown_super+0x47/0x120 kill_anon_super+0x14/0x30 ceph_kill_sb+0x36/0x90 [ceph] deactivate_locked_super+0x29/0x60 cleanup_mnt+0xb8/0x140 task_work_run+0x67/0xb0 exit_to_user_mode_prepare+0x23d/0x240 syscall_exit_to_user_mode+0x25/0x60 do_syscall_64+0x40/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fd83dc39e9b Later the kernel will crash when iput() the inodes and dereferencing the "sb->s_master_keys", which has been released by the generic_shutdown_super().

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 disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: ceph: drop messages from MDS when unmounting When unmounting all the dirty buffers will be flushed and after the last osd request is finished the last reference of the i_count will be released. Then it will flush the dirty cap/snap to MDSs, and the unmounting won't wait the possible acks, which will ihold the inodes when updating the metadata locally but makes no sense any more, of this. This will make the evict_inodes() to skip these inodes. If encrypt is enabled the kernel generate a warning when removing the encrypt keys when the skipped inodes still hold the keyring: WARNING: CPU: 4 PID: 168846 at fs/crypto/keyring.c:242 fscrypt_destroy_keyring+0x7e/0xd0 CPU: 4 PID: 168846 Comm: umount Tainted: G S 6.1.0-rc5-ceph-g72ead199864c #1 Hardware name: Supermicro SYS-5018R-WR/X10SRW-F, BIOS 2.0 12/17/2015 RIP: 0010:fscrypt_destroy_keyring+0x7e/0xd0 RSP: 0018:ffffc9000b277e28 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff88810d52ac00 RCX: ffff88810b56aa00 RDX: 0000000080000000 RSI: ffffffff822f3a09 RDI: ffff888108f59000 RBP: ffff8881d394fb88 R08: 0000000000000028 R09: 0000000000000000 R10: 0000000000000001 R11: 11ff4fe6834fcd91 R12: ffff8881d394fc40 R13: ffff888108f59000 R14: ffff8881d394f800 R15: 0000000000000000 FS: 00007fd83f6f1080(0000) GS:ffff88885fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f918d417000 CR3: 000000017f89a005 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> generic_shutdown_super+0x47/0x120 kill_anon_super+0x14/0x30 ceph_kill_sb+0x36/0x90 [ceph] deactivate_locked_super+0x29/0x60 cleanup_mnt+0xb8/0x140 task_work_run+0x67/0xb0 exit_to_user_mode_prepare+0x23d/0x240 syscall_exit_to_user_mode+0x25/0x60 do_syscall_64+0x40/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fd83dc39e9b Later the kernel will crash when iput() the inodes and dereferencing the "sb->s_master_keys", which has been released by the generic_shutdown_super().

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 disrupt the affected service.

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 → disrupt the affected service
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.
Denial of service
A

Official authority intelligence

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

BSI · German · WID-SEC-W-2024-0534Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2022-41409 Référence CVE CVE-2022-41848 https://www.cve.org/CVERecord?id=CVE-2022-41848 Référence CVE CVE-2022-44032 https://www.cve.org/CVERecord?id=CVE-2022-44032 Référence CVE CVE-2022-44033 https://www.cve.org/CVERecord?id=CVE-2022-44033 Référence CVE CVE-2022-44034 https://www.cve.org/CVERecord?id=CVE-2022-44034 Référence CVE CVE-2022-4543 https://www.cve.org/CVERecord?id=CVE-2022-4543 Référence CVE CVE-2022-45885 https://www.cve.org/CVERecord?id=CVE-2022-45885 Référence CVE CVE-2022-45888 https://www.cve.org/CVERecord?id=CVE-2022-45888 Référence CVE CVE-2022-48064 https://www.cve.org/CVERecord?id=CVE-2022-48064 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2022-48633 https://www.cve.org/CVERecord?id=CVE-2022-48633 Référence CVE CVE-2022-48646 https://www.cve.org/CVERecord?id=CVE-2022-48646 Référence CVE CVE-2022-48667 https://www.cve.org/CVERecord?id=CVE-2022-48667 Référence CVE CVE-2022-48668 https://www.cve.org/CVERecord?id=CVE-2022-48668 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48706 https://www.cve.org/CVERecord?id=CVE-2022-48706 Référence CVE CVE-2022-48744 https://www.cve.org/CVERecord?id=CVE-2022-48744 Référence CVE CVE-2022-48766 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2022-41409 Référence CVE CVE-2022-41848 https://www.cve.org/CVERecord?id=CVE-2022-41848 Référence CVE CVE-2022-44032 https://www.cve.org/CVERecord?id=CVE-2022-44032 Référence CVE CVE-2022-44033 https://www.cve.org/CVERecord?id=CVE-2022-44033 Référence CVE CVE-2022-44034 https://www.cve.org/CVERecord?id=CVE-2022-44034 Référence CVE CVE-2022-4543 https://www.cve.org/CVERecord?id=CVE-2022-4543 Référence CVE CVE-2022-45885 https://www.cve.org/CVERecord?id=CVE-2022-45885 Référence CVE CVE-2022-45888 https://www.cve.org/CVERecord?id=CVE-2022-45888 Référence CVE CVE-2022-48064 https://www.cve.org/CVERecord?id=CVE-2022-48064 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2022-48633 https://www.cve.org/CVERecord?id=CVE-2022-48633 Référence CVE CVE-2022-48646 https://www.cve.org/CVERecord?id=CVE-2022-48646 Référence CVE CVE-2022-48667 https://www.cve.org/CVERecord?id=CVE-2022-48667 Référence CVE CVE-2022-48668 https://www.cve.org/CVERecord?id=CVE-2022-48668 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48706 https://www.cve.org/CVERecord?id=CVE-2022-48706 Référence CVE CVE-2022-48744 https://www.cve.org/CVERecord?id=CVE-2022-48744 Référence CVE CVE-2022-48766 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2021-47182 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2021-47189 https://www.cve.org/CVERecord?id=CVE-2021-47189 Référence CVE CVE-2021-47202 https://www.cve.org/CVERecord?id=CVE-2021-47202 Référence CVE CVE-2022-0487 https://www.cve.org/CVERecord?id=CVE-2022-0487 Référence CVE CVE-2022-4744 https://www.cve.org/CVERecord?id=CVE-2022-4744 Référence CVE CVE-2022-48626 https://www.cve.org/CVERecord?id=CVE-2022-48626 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2022-48629 https://www.cve.org/CVERecord?id=CVE-2022-48629 Référence CVE CVE-2022-48630 https://www.cve.org/CVERecord?id=CVE-2022-48630 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-1192 https://www.cve.org/CVERecord?id=CVE-2023-1192 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-4881 https://www.cve.org/CVERecord?id=CVE-2023-4881 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-20

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

ord?id=CVE-2021-47102 Référence CVE CVE-2021-47104 https://www.cve.org/CVERecord?id=CVE-2021-47104 Référence CVE CVE-2021-47105 https://www.cve.org/CVERecord?id=CVE-2021-47105 Référence CVE CVE-2021-47107 https://www.cve.org/CVERecord?id=CVE-2021-47107 Référence CVE CVE-2021-47108 https://www.cve.org/CVERecord?id=CVE-2021-47108 Référence CVE CVE-2022-20154 https://www.cve.org/CVERecord?id=CVE-2022-20154 Référence CVE CVE-2022-4744 https://www.cve.org/CVERecord?id=CVE-2022-4744 Référence CVE CVE-2022-48626 https://www.cve.org/CVERecord?id=CVE-2022-48626 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2022-48629 https://www.cve.org/CVERecord?id=CVE-2022-48629 Référence CVE CVE-2022-48630 https://www.cve.org/CVERecord?id=CVE-2022-48630 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-42753 https://www.cve.org/CVERecord?id=CVE-2023-42753 Référence CVE CVE-2023-4881 https://www.cve.org/CVERecord?id=CVE-2

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

d?id=CVE-2021-47054 Référence CVE CVE-2021-47060 https://www.cve.org/CVERecord?id=CVE-2021-47060 Référence CVE CVE-2021-47061 https://www.cve.org/CVERecord?id=CVE-2021-47061 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47078 https://www.cve.org/CVERecord?id=CVE-2021-47078 Référence CVE CVE-2021-47083 https://www.cve.org/CVERecord?id=CVE-2021-47083 Référence CVE CVE-2022-20154 https://www.cve.org/CVERecord?id=CVE-2022-20154 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-5197 https://www.cve.org/CVERecord?id=CVE-2023-5197 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CV

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
2f2dc053404febedc9c273452d9d518fb31fde72 < 89744b64914426cbabceb3d8a149176b5dafdfb5; 2f2dc053404febedc9c273452d9d518fb31fde72 < 47f82395f04a976d4fa97de7f2acffa1c1096571; 2f2dc053404febedc9c273452d9d518fb31fde72 < e3dfcab2080dc1f9a4b09cc1327361bc2845bfcd; 2.6.34
Fixed
< 2.6.34; 6.1.56 ≤ 6.1.*; 6.5.6 ≤ 6.5.*; 6.6 ≤ *
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 2 Mar 2024 · Last source change 11 Aug 2026, 02:05 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-51323
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
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-48628 · cve.blacktree.nl