Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-48808: net: dsa: fix panic when DSA master device unbinds on shutdown

Noroxi assessment

Priority: Monitor (action score 22/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.27% (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 89b60402d43cdab4387dbbf24afebda5cf092ae7, ee534378f00561207656663d93907583958339ae, ff45899e732e57088985e3a497b1d9100571c0f5.

Low priority for now. Upgrade to Linux Linux 89b60402d43cdab4387dbbf24afebda5cf092ae7, ee534378f00561207656663d93907583958339ae, ff45899e732e57088985e3a497b1d9100571c0f5 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: 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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 16, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 19th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2022-48808

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel5.15 and later · before 5.15.155
  • linux linux kernel5.16 and later · before 5.16.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

    • 5.15affected
    • 0650bf52b31ff35dc6430fc2e37969c36baba724 and later · before ff45899e732e57088985e3a497b1d9100571c0f5affected · git
    • 0650bf52b31ff35dc6430fc2e37969c36baba724 and later · before 89b60402d43cdab4387dbbf24afebda5cf092ae7affected · git
    • 0650bf52b31ff35dc6430fc2e37969c36baba724 and later · before ee534378f00561207656663d93907583958339aeaffected · git
    • before 5.15not affected · semver
    • 5.15.155 and later · up to and including 5.15.*not affected · semver
    • 5.16.10 and later · up to and including 5.16.*not affected · semver
    • 5.17 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.16.10-15.16.10-1
openSUSE:Leap 15.5dtb-aarch64before 5.14.21-150500.55.80.15.14.21-150500.55.80.1
openSUSE:Leap 15.5kernel-64kbbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap 15.5kernel-azurebefore 5.14.21-150500.33.66.15.14.21-150500.33.66.1
openSUSE:Leap 15.5kernel-debugbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap 15.5kernel-docsbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap 15.5kernel-kvmsmallbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap 15.5kernel-obs-buildbefore 5.14.21-150500.55.80.15.14.21-150500.55.80.1
openSUSE:Leap 15.5kernel-obs-qabefore 5.14.21-150500.55.80.15.14.21-150500.55.80.1
openSUSE:Leap 15.5kernel-rt_debugbefore 5.14.21-150500.13.67.35.14.21-150500.13.67.3
openSUSE:Leap 15.5kernel-sourcebefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap 15.5kernel-source-azurebefore 5.14.21-150500.33.66.15.14.21-150500.33.66.1
openSUSE:Leap 15.5kernel-source-rtbefore 5.14.21-150500.13.67.35.14.21-150500.13.67.3
openSUSE:Leap 15.5kernel-symsbefore 5.14.21-150500.55.80.15.14.21-150500.55.80.1
openSUSE:Leap 15.5kernel-syms-azurebefore 5.14.21-150500.33.66.15.14.21-150500.33.66.1
openSUSE:Leap 15.5kernel-syms-rtbefore 5.14.21-150500.13.67.15.14.21-150500.13.67.1
openSUSE:Leap 15.5kernel-zfcpdumpbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap Micro 5.5kernel-defaultbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
openSUSE:Leap Micro 5.5kernel-default-basebefore 5.14.21-150500.55.80.2.150500.6.35.65.14.21-150500.55.80.2.150500.6.35.6
openSUSE:Leap Micro 5.5kernel-rtbefore 5.14.21-150500.13.67.35.14.21-150500.13.67.3
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_19before 1-150500.11.3.21-150500.11.3.2
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5-RT_Update_19before 1-150500.11.3.21-150500.11.3.2
SUSE:Linux Enterprise Micro 5.5kernel-defaultbefore 5.14.21-150500.55.80.25.14.21-150500.55.80.2
SUSE:Linux Enterprise Micro 5.5kernel-default-basebefore 5.14.21-150500.55.80.2.150500.6.35.65.14.21-150500.55.80.2.150500.6.35.6

+13

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-2022-48806Jul 16, 2024 · eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
    22Monitor
  • ← EarlierCVE-2022-48807Jul 16, 2024 · ice: Fix KASAN error in LAG NETDEV_UNREGISTER handler
    22Monitor
  • Later →CVE-2022-48809Jul 16, 2024 · net: fix a memleak when uncloning an skb dst and its metadata
    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 / packageFixed versionSource
Linux Linux89b60402d43cdab4387dbbf24afebda5cf092ae7Vendor (CNA)
Linux Linuxee534378f00561207656663d93907583958339aeVendor (CNA)
Linux Linuxff45899e732e57088985e3a497b1d9100571c0f5Vendor (CNA)
debian:linux5.16.10-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch645.14.21-150500.55.80.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-64kb5.14.21-150500.55.80.2 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-azure5.14.21-150500.33.66.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-debug5.14.21-150500.55.80.2 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-default5.14.21-150500.55.80.2 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:kernel-default-base5.14.21-150500.55.80.2.150500.6.35.6 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:kernel-rt5.14.21-150500.13.67.3 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:kernel-rt_debug5.14.21-150500.13.67.3 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-azure5.14.21-150500.33.66.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-rt5.14.21-150500.13.67.3 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-azure5.14.21-150500.33.66.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-rt5.14.21-150500.13.67.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:kernel-64kb5.14.21-150500.55.80.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)
suse:kernel-azure5.14.21-150500.33.66.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-default5.14.21-150500.55.80.2 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-default-base5.14.21-150500.55.80.2.150500.6.35.6 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5-RT_Update_191-150500.11.3.2 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-rt5.14.21-150500.13.67.3 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-rt_debug5.14.21-150500.13.67.3 · SUSE:Real Time Module 15 SP5Package registry (OSV)
suse:kernel-source5.14.21-150500.55.80.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)
suse:kernel-source-azure5.14.21-150500.33.66.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-source-rt5.14.21-150500.13.67.3 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-syms-azure5.14.21-150500.33.66.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-syms-rt5.14.21-150500.13.67.1 · SUSE:Real Time Module 15 SP5Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

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

  1. Fix✗ → ✓

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

References

Show all references (2 more)

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

All records