CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
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.23% (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 02ee1976edb21a96ce8e3fd4ef563f14cc16d041, 5d8254e012996cee1a0f9cc920531cb7e4d9a011, 626dfed5fa3bfb41e0dffd796032b555b69f9cde; Azure Linux 3.0 ARM 6.6.43.1-7; Azure Linux 3.0 x64 6.6.43.1-7.
Low priority for now. Upgrade to Linux Linux 02ee1976edb21a96ce8e3fd4ef563f14cc16d041, 5d8254e012996cee1a0f9cc920531cb7e4d9a011, 626dfed5fa3bfb41e0dffd796032b555b69f9cde; Azure Linux 3.0 ARM 6.6.43.1-7; Azure Linux 3.0 x64 6.6.43.1-7 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, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket When using a BPF program on kernel_connect(), the call can return -EPERM. This causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing the kernel to potentially freeze up. Neil suggested: This will propagate -EPERM up into other layers which might not be ready to handle it. It might be safer to map EPERM to an error we would be more likely to expect from the network system - such as ECONNREFUSED or ENETDOWN. ECONNREFUSED as error seems reasonable. For programs setting a different error can be out of reach (see handling in 4fbac77d2d09) in particular on kernels which do not have f10d05966196 ("bpf: Make BPF_PROG_RUN_ARRAY return -err instead of allow boolean"), thus given that it is better to simply remap for consistent behavior. UDP does handle EPERM in xs_udp_send_request().
- Published
- Aug 7, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-835
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.17 and later · before 6.1.100
- linux linux kernel6.2 and later · before 6.6.41
- linux linux kernel6.7 and later · before 6.9.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
- 4.17affected
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before bc790261218952635f846aaf90bcc0974f6f62c6affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before 934247ea65bc5eca8bdb7f8c0ddc15cef992a5d6affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before 02ee1976edb21a96ce8e3fd4ef563f14cc16d041affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before 5d8254e012996cee1a0f9cc920531cb7e4d9a011affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before f2431e7db0fe0daccb2f06bb0d23740affcd2fa6affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before d6c686c01c5f12ff8f7264e0ddf71df6cb0d4414affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before f388cfd913a2b96c05339a335f365795db1b36b6affected · git
- 4fbac77d2d092b475dda9eea66da674369665427 and later · before 626dfed5fa3bfb41e0dffd796032b555b69f9cdeaffected · git
- before 4.17not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.226-1 | 5.10.226-1 |
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.9.10-1 | 6.9.10-1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.84.1.el9_2 | 0:7.0.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
+54
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-42244Aug 7, 2024 · USB: serial: mos7840: fix crash on resume22Monitor
- ← EarlierCVE-2024-42245Aug 7, 2024 · Revert "sched/fair: Make sure to try to detach at least one movable task"22Monitor
- Later →CVE-2024-42247Aug 7, 2024 · wireguard: allowedips: avoid unaligned 64-bit memory accesses22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02ee1976edb21a96ce8e3fd4ef563f14cc16d041 | Vendor (CNA) |
| Linux Linux | 5d8254e012996cee1a0f9cc920531cb7e4d9a011 | Vendor (CNA) |
| Linux Linux | 626dfed5fa3bfb41e0dffd796032b555b69f9cde | Vendor (CNA) |
| Linux Linux | 934247ea65bc5eca8bdb7f8c0ddc15cef992a5d6 | Vendor (CNA) |
| Linux Linux | bc790261218952635f846aaf90bcc0974f6f62c6 | Vendor (CNA) |
| Linux Linux | d6c686c01c5f12ff8f7264e0ddf71df6cb0d4414 | Vendor (CNA) |
| Linux Linux | f2431e7db0fe0daccb2f06bb0d23740affcd2fa6 | Vendor (CNA) |
| Linux Linux | f388cfd913a2b96c05339a335f365795db1b36b6 | Vendor (CNA) |
| Azure Linux 3.0 ARM | 6.6.43.1-7 · kernel | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 6.6.43.1-7 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 5.15.167.1-1 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 5.15.167.1-1 · kernel | Microsoft (MSRC) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package 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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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.
- CVE-2024-2703298 days apartf2fs: fix to avoid potential panic during recovery25Monitor
- CVE-2022-48635101 days apartfsdax: Fix infinite loop in dax_iomap_rw()24Monitor
- CVE-2024-422400 days apartx86/bhi: Avoid warning in #DB handler due to BHI mitigation22Monitor
- CVE-2024-410889 days apartcan: mcp251xfd: fix infinite loop when xmit fails22Monitor
- CVE-2024-4382810 days apartext4: fix infinite loop when replaying fast_commit22Monitor
- CVE-2022-4886222 days apartvhost: fix hung thread due to erroneous iotlb entries22Monitor
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)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/5d8254e012996cee1a0f9cc920531cb7e4d9a011
- git.kernel.org/stable/c/626dfed5fa3bfb41e0dffd796032b555b69f9cde
- git.kernel.org/stable/c/934247ea65bc5eca8bdb7f8c0ddc15cef992a5d6
- git.kernel.org/stable/c/bc790261218952635f846aaf90bcc0974f6f62c6
- git.kernel.org/stable/c/d6c686c01c5f12ff8f7264e0ddf71df6cb0d4414
- git.kernel.org/stable/c/f2431e7db0fe0daccb2f06bb0d23740affcd2fa6
- git.kernel.org/stable/c/f388cfd913a2b96c05339a335f365795db1b36b6
- lists.debian.org/debian-lts-announce/2024/10/msg00003.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.