CVE-2024-0607 [Medium] | Denial of Service in Linux Kernel

A flaw was found in the Netfilter subsystem in the Linux kernel. The issue is in the nft_byteorder_eval() function, where the code iterates through a loop and writes to the `dst` array. On each iteration, 8 bytes are written, but `dst` is an array of u32, so each element only has space for 4 bytes. That means every iteration overwrites part of the previous element corrupting this array of u32. This flaw allows a local user to cause a denial of service or potentially break NetFilter functionality.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.05%	0.02%	-0.03%
2	2025-11-18	0.04%	0.05%	+0.01%
3	2025-03-30	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.05%

0.02%

-0.03%

2025-11-18

0.04%

0.05%

+0.01%

2025-03-30

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.6	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	4.7	[email protected]
6.6	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	4.7	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.6

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

4.7

[email protected]

6.6

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

4.7

[email protected]

OS Trackers for CVE-2024-0607

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2024-0607 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-2024-0607
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2024-0607
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2024-0607/
`ubuntu`	medium	CVE-2024-0607 medium priority: Ubuntu including 167 source packages (linux, linux-allwinner, …), 1872 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1427, released 188, ignored 145, not-affected 95, needed 15, needs-triage 2.	https://ubuntu.com/security/CVE-2024-0607

Affected software / configurations for CVE-2024-0607

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 6.7	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.7	cpe:2.3:o:linux:linux_kernel:6.7:rc1::::::
fedoraproject	fedora	39	cpe:2.3:o:fedoraproject:fedora:39:::::::*
redhat	enterprise_linux	8.0	cpe:2.3:o:redhat:enterprise_linux:8.0:::::::*
redhat	enterprise_linux	9.0	cpe:2.3:o:redhat:enterprise_linux:9.0:::::::*

References for CVE-2024-0607

URL	Tags
https://access.redhat.com/security/cve/CVE-2024-0607	Third Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2258635	Issue Tracking Patch Third Party Advisory
https://github.com/torvalds/linux/commit/c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63	Patch
https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html

URL

CVE-2024-0607 | Kernel: nf_tables: pointer math issue in nft_byteorder_eval()

Exploit prediction scoring system (EPSS) score for CVE-2024-0607

Common vulnerability scoring system (CVSS) metrics for CVE-2024-0607

Weakness enumeration for CVE-2024-0607

OS Trackers for CVE-2024-0607

Affected software / configurations for CVE-2024-0607

References for CVE-2024-0607