CVE-2025-21838 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: core: flush gadget workqueue after device removal device_del() can lead to new work being scheduled in gadget->work workqueue. This is observed, for example, with the dwc3 driver with the following call stack: device_del() gadget_unbind_driver() usb_gadget_disconnect_locked() dwc3_gadget_pullup() dwc3_gadget_soft_disconnect() usb_gadget_set_state() schedule_work(&gadget->work) Move flush_work() after device_del() to ensure the workqueue is cleaned up.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.04%	0.18%	+0.14%
2	2026-03-31	0.05%	0.04%	-0.01%
3	2026-01-01	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.04%

0.18%

+0.14%

2026-03-31

0.05%

0.04%

-0.01%

2026-01-01

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-21838

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-21838 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1.	https://security-tracker.debian.org/tracker/CVE-2025-21838
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-21838
`suse`	medium	CVE-2025-21838 severity moderate: SUSE including 415 source package names (2.1.3-6.11:kernel-default-6.4.0-28.1, 2.1.3-6.12:kernel-default-base-6.4.0-28.1.21.6, …), 825 product×package rows across 148 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (148 product lines)): Fixed 361, Known Not Affected 233, Known Affected 231.	https://www.suse.com/security/cve/CVE-2025-21838/
`ubuntu`	medium	CVE-2025-21838 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 154, released 135, needed 74, not-affected 43.	https://ubuntu.com/security/CVE-2025-21838

Affected software / configurations for CVE-2025-21838

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.12, < 6.1.130	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.80	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.16	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.13.4	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.14	cpe:2.3:o:linux:linux_kernel:6.14:rc1::::::
linux	linux_kernel	6.14	cpe:2.3:o:linux:linux_kernel:6.14:rc2::::::

References for CVE-2025-21838

URL	Tags
https://git.kernel.org/stable/c/399a45e5237ca14037120b1b895bd38a3b4492ea	Patch
https://git.kernel.org/stable/c/859cb45aefa6de823b2fa7f229fe6d9562c9f3b7	Patch
https://git.kernel.org/stable/c/97695b5a1b5467a4f91194db12160f56da445dfe	Patch
https://git.kernel.org/stable/c/e3bc1a9a67ce33a2e761e6e7b7c2afc6cb9b7266	Patch
https://git.kernel.org/stable/c/f894448f3904d7ad66fecef8f01fe0172629e091	Patch
https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html

URL

CVE-2025-21838 | usb: gadget: core: flush gadget workqueue after device removal

Exploit prediction scoring system (EPSS) score for CVE-2025-21838

Common vulnerability scoring system (CVSS) metrics for CVE-2025-21838

Weakness enumeration for CVE-2025-21838

OS Trackers for CVE-2025-21838

Affected software / configurations for CVE-2025-21838

References for CVE-2025-21838