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

net: dsa: fix panic when DSA master device unbinds on shutdown

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 9 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-53687

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: net: dsa: fix panic when DSA master device unbinds on shutdown Rafael reports that on a system with LX2160A and Marvell DSA switches, if a reboot occurs while the DSA master (dpaa2-eth) is up, the following panic can be seen: systemd-shutdown[1]: Rebooting. Unable to handle kernel paging request at virtual address 00a0000800000041 [00a0000800000041] address between user and kernel address ranges Internal error: Oops: 96000004 [#1] PREEMPT SMP CPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32 pc : dsa_slave_netdevice_event+0x130/0x3e4 lr : raw_notifier_call_chain+0x50/0x6c Call trace: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17c It can be seen from the stack trace that the problem is that the deregistration of the master causes a dev_close(), which gets notified as NETDEV_GOING_DOWN to dsa_slave_netdevice_event(). But dsa_switch_shutdown() has already run, and this has unregistered the DSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to call dev_close_many() on those slave interfaces, leading to the problem. The previous attempt to avoid the NETDEV_GOING_DOWN on the master after dsa_switch_shutdown() was called seems improper. Unregistering the slave interfaces is unnecessary and unhelpful. Instead, after the slaves have stopped being uppers of the DSA master, we can now reset to NULL the master->dsa_ptr pointer, which will make DSA start ignoring all future notifier events on the master.

What

In the Linux kernel, the following vulnerability has been resolved: net: dsa: fix panic when DSA master device unbinds on shutdown Rafael reports that on a system with LX2160A and Marvell DSA switches, if a reboot occurs while the DSA master (dpaa2-eth) is up, the following panic can be seen: systemd-shutdown[1]: Rebooting. Unable to handle kernel paging request at virtual address 00a0000800000041 [00a0000800000041] address between user and kernel address ranges Internal error: Oops: 96000004 [#1] PREEMPT SMP CPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32 pc : dsa_slave_netdevice_event+0x130/0x3e4 lr : raw_notifier_call_chain+0x50/0x6c Call trace: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17c It can be seen from the stack trace that the problem is that the deregistration of the master causes a dev_close(), which gets notified as NETDEV_GOING_DOWN to dsa_slave_netdevice_event(). But dsa_switch_shutdown() has already run, and this has unregistered the DSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to call dev_close_many() on those slave interfaces, leading to the problem. The previous attempt to avoid the NETDEV_GOING_DOWN on the master after dsa_switch_shutdown() was called seems improper. Unregistering the slave interfaces is unnecessary and unhelpful. Instead, after the slaves have stopped being uppers of the DSA master, we can now reset to NULL the master->dsa_ptr pointer, which will make DSA start ignoring all future notifier events on the master.

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: net: dsa: fix panic when DSA master device unbinds on shutdown Rafael reports that on a system with LX2160A and Marvell DSA switches, if a reboot occurs while the DSA master (dpaa2-eth) is up, the following panic can be seen: systemd-shutdown[1]: Rebooting. Unable to handle kernel paging request at virtual address 00a0000800000041 [00a0000800000041] address between user and kernel address ranges Internal error: Oops: 96000004 [#1] PREEMPT SMP CPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32 pc : dsa_slave_netdevice_event+0x130/0x3e4 lr : raw_notifier_call_chain+0x50/0x6c Call trace: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17c It can be seen from the stack trace that the problem is that the deregistration of the master causes a dev_close(), which gets notified as NETDEV_GOING_DOWN to dsa_slave_netdevice_event(). But dsa_switch_shutdown() has already run, and this has unregistered the DSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to call dev_close_many() on those slave interfaces, leading to the problem. The previous attempt to avoid the NETDEV_GOING_DOWN on the master after dsa_switch_shutdown() was called seems improper. Unregistering the slave interfaces is unnecessary and unhelpful. Instead, after the slaves have stopped being uppers of the DSA master, we can now reset to NULL the master->dsa_ptr pointer, which will make DSA start ignoring all future notifier events on the master.

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.

BSI · German · WID-SEC-W-2024-1625Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

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

ord?id=CVE-2022-38457 Référence CVE CVE-2022-40133 https://www.cve.org/CVERecord?id=CVE-2022-40133 Référence CVE CVE-2022-4382 https://www.cve.org/CVERecord?id=CVE-2022-4382 Référence CVE CVE-2022-48645 https://www.cve.org/CVERecord?id=CVE-2022-48645 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48706 https://www.cve.org/CVERecord?id=CVE-2022-48706 Référence CVE CVE-2022-48791 https://www.cve.org/CVERecord?id=CVE-2022-48791 Référence CVE CVE-2022-48802 https://www.cve.org/CVERecord?id=CVE-2022-48802 Référence CVE CVE-2022-48805 https://www.cve.org/CVERecord?id=CVE-2022-48805 Référence CVE CVE-2022-48808 https://www.cve.org/CVERecord?id=CVE-2022-48808 Référence CVE CVE-2022-48839 https://www.cve.org/CVERecord?id=CVE-2022-48839 Référence CVE CVE-2022-48853 https://www.cve.org/CVERecord?id=CVE-2022-48853 Référence CVE CVE-2022-48865 https://www.cve.org/CVERecord?id=CVE-2022-48865 Référence CVE CVE-2022-48868 https://www.cve.org/CVERecord?id=CVE-2022-48868 Référence CVE CVE-2022-48869 https://www.cve.org/CVERecord?id=CVE-2022-48869 Référence CVE CVE-2022-48870 https://www.cve.org/CVERecord?id=CVE-2022-48870 Référence CVE CVE-2022-48871 https://www.cve.org/CVERecord?id=CVE-2022-48871 Référence CVE CVE-2022-48872 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0799Multiples vulnérabilités dans le noyau Linux d'Ubuntu

7019-1 Bulletin de sécurité Ubuntu USN-7020-1 du 18 septembre 2024 https://ubuntu.com/security/notices/USN-7020-1 Bulletin de sécurité Ubuntu USN-7021-1 du 18 septembre 2024 https://ubuntu.com/security/notices/USN-7021-1 Bulletin de sécurité Ubuntu USN-7022-1 du 18 septembre 2024 https://ubuntu.com/security/notices/USN-7022-1 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48772 https://www.cve.org/CVERecord?id=CVE-2022-48772 Référence CVE CVE-2022-48791 https://www.cve.org/CVERecord?id=CVE-2022-48791 Référence CVE CVE-2022-48808 https://www.cve.org/CVERecord?id=CVE-2022-48808 Référence CVE CVE-2022-48863 https://www.cve.org/CVERecord?id=CVE-2022-48863 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52629 https://www.cve.org/CVERecord?id=CVE-2023-52629 Référence CVE CVE-2023-52699 https://www.cve.org/CVERecord?id=CVE-2023-52699 Référence CVE CVE-2023-52752 https://www.cve.org/CVERecord?id=CVE-2023-52752 Référence CVE CVE-2023-52760 https://www.cve.org/CVERecord?id=CVE-2023-52760 Référence CVE CVE-2023-52880 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48778 Référence CVE CVE-2022-48786 https://www.cve.org/CVERecord?id=CVE-2022-48786 Référence CVE CVE-2022-48787 https://www.cve.org/CVERecord?id=CVE-2022-48787 Référence CVE CVE-2022-48788 https://www.cve.org/CVERecord?id=CVE-2022-48788 Référence CVE CVE-2022-48789 https://www.cve.org/CVERecord?id=CVE-2022-48789 Référence CVE CVE-2022-48790 https://www.cve.org/CVERecord?id=CVE-2022-48790 Référence CVE CVE-2022-48798 https://www.cve.org/CVERecord?id=CVE-2022-48798 Référence CVE CVE-2022-48802 https://www.cve.org/CVERecord?id=CVE-2022-48802 Référence CVE CVE-2022-48805 https://www.cve.org/CVERecord?id=CVE-2022-48805 Référence CVE CVE-2022-48808 https://www.cve.org/CVERecord?id=CVE-2022-48808 Référence CVE CVE-2022-48811 https://www.cve.org/CVERecord?id=CVE-2022-48811 Référence CVE CVE-2022-48822 https://www.cve.org/CVERecord?id=CVE-2022-48822 Référence CVE CVE-2022-48823 https://www.cve.org/CVERecord?id=CVE-2022-48823 Référence CVE CVE-2022-48824 https://www.cve.org/CVERecord?id=CVE-2022-48824 Référence CVE CVE-2022-48827 https://www.cve.org/CVERecord?id=CVE-2022-48827 Référence CVE CVE-2022-48834 https://www.cve.org/CVERecord?id=CVE-2022-48834 Référence CVE CVE-2022-48835 https://www.cve.org/CVERecord?id=CVE-2022-48835 Référence CVE CVE-2022-48836 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0645Multiples vulnérabilités dans le noyau Linux d'Ubuntu

/notices/USN-6938-1 Référence CVE CVE-2021-46932 https://www.cve.org/CVERecord?id=CVE-2021-46932 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=CVE-2021-46960 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47194 https://www.cve.org/CVERecord?id=CVE-2021-47194 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48619 https://www.cve.org/CVERecord?id=CVE-2022-48619 Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2022-48808 https://www.cve.org/CVERecord?id=CVE-2022-48808 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52449 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
0650bf52b31ff35dc6430fc2e37969c36baba724 < ff45899e732e57088985e3a497b1d9100571c0f5; 0650bf52b31ff35dc6430fc2e37969c36baba724 < 89b60402d43cdab4387dbbf24afebda5cf092ae7; 0650bf52b31ff35dc6430fc2e37969c36baba724 < ee534378f00561207656663d93907583958339ae; 5.15
Fixed
< 5.15; 5.15.155 ≤ 5.15.*; 5.16.10 ≤ 5.16.*; 5.17 ≤ *
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 16 Jul 2024 · Last source change 11 May 2026, 18:47 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-53687
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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-53687↗CVE authority or vendor 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-48808 · cve.blacktree.nl