CVE-2022-49838 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: sctp: clear out_curr if all frag chunks of current msg are pruned A crash was reported by Zhen Chen: list_del corruption, ffffa035ddf01c18->next is NULL WARNING: CPU: 1 PID: 250682 at lib/list_debug.c:49 __list_del_entry_valid+0x59/0xe0 RIP: 0010:__list_del_entry_valid+0x59/0xe0 Call Trace: sctp_sched_dequeue_common+0x17/0x70 [sctp] sctp_sched_fcfs_dequeue+0x37/0x50 [sctp] sctp_outq_flush_data+0x85/0x360 [sctp] sctp_outq_uncork+0x77/0xa0 [sctp] sctp_cmd_interpreter.constprop.0+0x164/0x1450 [sctp] sctp_side_effects+0x37/0xe0 [sctp] sctp_do_sm+0xd0/0x230 [sctp] sctp_primitive_SEND+0x2f/0x40 [sctp] sctp_sendmsg_to_asoc+0x3fa/0x5c0 [sctp] sctp_sendmsg+0x3d5/0x440 [sctp] sock_sendmsg+0x5b/0x70 and in sctp_sched_fcfs_dequeue() it dequeued a chunk from stream out_curr outq while this outq was empty. Normally stream->out_curr must be set to NULL once all frag chunks of current msg are dequeued, as we can see in sctp_sched_dequeue_done(). However, in sctp_prsctp_prune_unsent() as it is not a proper dequeue, sctp_sched_dequeue_done() is not called to do this. This patch is to fix it by simply setting out_curr to NULL when the last frag chunk of current msg is dequeued from out_curr stream in sctp_prsctp_prune_unsent().

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-02-25	0.03%	0.05%	+0.02%
2	2025-11-11	0.09%	0.03%	-0.06%
3	2025-07-16	—	0.09%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-02-25

0.03%

0.05%

+0.02%

2025-11-11

0.09%

0.03%

-0.06%

2025-07-16

—

0.09%

—

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-2022-49838

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49838 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-49838
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49838
`suse`	medium	CVE-2022-49838 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 267 product×package rows across 51 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 15 SP7, … (51 product lines)): Known Not Affected 267.	https://www.suse.com/security/cve/CVE-2022-49838/
`ubuntu`	medium	CVE-2022-49838 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 147, released 116, not-affected 105, needed 37, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49838

Affected software / configurations for CVE-2022-49838

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.15, < 5.10.156	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.81	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc1::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc2::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc3::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc4::::::

References for CVE-2022-49838

URL	Tags
https://git.kernel.org/stable/c/2ea600b598dd3e061854dd4dd5b4c815397dfcea	Patch
https://git.kernel.org/stable/c/2f201ae14ae0f91dbf1cffea7bb1e29e81d4d108	Patch
https://git.kernel.org/stable/c/3eff34e01062ec08fbb45ce2baaaa644550be821	Patch
https://git.kernel.org/stable/c/e27458b18b35caee4b27b37a4a9c503b93cae5cc	Patch

URL

CVE-2022-49838 | sctp: clear out_curr if all frag chunks of current msg are pruned

Exploit prediction scoring system (EPSS) score for CVE-2022-49838

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49838

Weakness enumeration for CVE-2022-49838

OS Trackers for CVE-2022-49838

Affected software / configurations for CVE-2022-49838

References for CVE-2022-49838