CVE-2021-47399: ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup
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.24% (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 20f6c4a31a525edd9ea6243712b868ba0e4e331e, 2744341dd52e935344ca1b4bf189ba0d182a3e8e, 513e605d7a9ce136886cb42ebb2c40e9a6eb6333.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 20f6c4a31a525edd9ea6243712b868ba0e4e331e, 2744341dd52e935344ca1b4bf189ba0d182a3e8e, 513e605d7a9ce136886cb42ebb2c40e9a6eb6333 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: ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup The ixgbe driver currently generates a NULL pointer dereference with some machine (online cpus < 63). This is due to the fact that the maximum value of num_xdp_queues is nr_cpu_ids. Code is in "ixgbe_set_rss_queues"". Here's how the problem repeats itself: Some machine (online cpus < 63), And user set num_queues to 63 through ethtool. Code is in the "ixgbe_set_channels", adapter->ring_feature[RING_F_FDIR].limit = count; It becomes 63. When user use xdp, "ixgbe_set_rss_queues" will set queues num. adapter->num_rx_queues = rss_i; adapter->num_tx_queues = rss_i; adapter->num_xdp_queues = ixgbe_xdp_queues(adapter); And rss_i's value is from f = &adapter->ring_feature[RING_F_FDIR]; rss_i = f->indices = f->limit; So "num_rx_queues" > "num_xdp_queues", when run to "ixgbe_xdp_setup", for (i = 0; i < adapter->num_rx_queues; i++) if (adapter->xdp_ring[i]->xsk_umem) It leads to panic. Call trace: [exception RIP: ixgbe_xdp+368] RIP: ffffffffc02a76a0 RSP: ffff9fe16202f8d0 RFLAGS: 00010297 RAX: 0000000000000000 RBX: 0000000000000020 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000000000000001c RDI: ffffffffa94ead90 RBP: ffff92f8f24c0c18 R8: 0000000000000000 R9: 0000000000000000 R10: ffff9fe16202f830 R11: 0000000000000000 R12: ffff92f8f24c0000 R13: ffff9fe16202fc01 R14: 000000000000000a R15: ffffffffc02a7530 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 7 [ffff9fe16202f8f0] dev_xdp_install at ffffffffa89fbbcc 8 [ffff9fe16202f920] dev_change_xdp_fd at ffffffffa8a08808 9 [ffff9fe16202f960] do_setlink at ffffffffa8a20235 10 [ffff9fe16202fa88] rtnl_setlink at ffffffffa8a20384 11 [ffff9fe16202fc78] rtnetlink_rcv_msg at ffffffffa8a1a8dd 12 [ffff9fe16202fcf0] netlink_rcv_skb at ffffffffa8a717eb 13 [ffff9fe16202fd40] netlink_unicast at ffffffffa8a70f88 14 [ffff9fe16202fd80] netlink_sendmsg at ffffffffa8a71319 15 [ffff9fe16202fdf0] sock_sendmsg at ffffffffa89df290 16 [ffff9fe16202fe08] __sys_sendto at ffffffffa89e19c8 17 [ffff9fe16202ff30] __x64_sys_sendto at ffffffffa89e1a64 18 [ffff9fe16202ff38] do_syscall_64 at ffffffffa84042b9 19 [ffff9fe16202ff50] entry_SYSCALL_64_after_hwframe at ffffffffa8c0008c So I fix ixgbe_max_channels so that it will not allow a setting of queues to be higher than the num_online_cpus(). And when run to ixgbe_xdp_setup, take the smaller value of num_rx_queues and num_xdp_queues.
- Published
- May 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-476
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 |
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.0affected
- 4a9b32f30f805ca596d76605903a48eab58e0b88 and later · before 20f6c4a31a525edd9ea6243712b868ba0e4e331eaffected · git
- 4a9b32f30f805ca596d76605903a48eab58e0b88 and later · before 2744341dd52e935344ca1b4bf189ba0d182a3e8eaffected · git
- 4a9b32f30f805ca596d76605903a48eab58e0b88 and later · before 513e605d7a9ce136886cb42ebb2c40e9a6eb6333affected · git
- before 5.0not affected · semver
- 5.10.71 and later · up to and including 5.10.*not affected · semver
- 5.14.10 and later · up to and including 5.14.*not affected · semver
- 5.15 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.0 and later · before 5.10.71
- linux linux kernel5.11 and later · before 5.14.10
- linux linux kernel5.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.14.12-1 | 5.14.12-1 |
| SUSE:Linux Enterprise High Availability Extension 12 SP5 | kernel-default | before 4.12.14-122.225.1 | 4.12.14-122.225.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_59 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-rt | before 4.12.14-10.197.1 | 4.12.14-10.197.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-rt_debug | before 4.12.14-10.197.1 | 4.12.14-10.197.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-source-rt | before 4.12.14-10.197.1 | 4.12.14-10.197.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-syms-rt | before 4.12.14-10.197.1 | 4.12.14-10.197.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-azure | before 4.12.14-16.194.1 | 4.12.14-16.194.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-source | before 4.12.14-122.225.1 | 4.12.14-122.225.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-source-azure | before 4.12.14-16.194.1 | 4.12.14-16.194.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-syms | before 4.12.14-122.225.1 | 4.12.14-122.225.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-syms-azure | before 4.12.14-16.194.1 | 4.12.14-16.194.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | kernel-docs | before 4.12.14-122.225.2 | 4.12.14-122.225.2 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | kernel-obs-build | before 4.12.14-122.225.1 | 4.12.14-122.225.1 |
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-2021-47397May 21, 2024 · sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb22Monitor
- ← EarlierCVE-2021-47398May 21, 2024 · RDMA/hfi1: Fix kernel pointer leak22Monitor
- Later →CVE-2021-47400May 21, 2024 · net: hns3: do not allow call hns3_nic_net_open repeatedly22Monitor
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 | 20f6c4a31a525edd9ea6243712b868ba0e4e331e | Vendor (CNA) |
| Linux Linux | 2744341dd52e935344ca1b4bf189ba0d182a3e8e | Vendor (CNA) |
| Linux Linux | 513e605d7a9ce136886cb42ebb2c40e9a6eb6333 | Vendor (CNA) |
| debian:linux | 5.14.12-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-azure | 4.12.14-16.194.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.225.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5 | Package registry (OSV) |
| suse:kernel-docs | 4.12.14-122.225.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 4.12.14-122.225.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:kernel-rt | 4.12.14-10.197.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-rt_debug | 4.12.14-10.197.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.225.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 4.12.14-16.194.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 4.12.14-10.197.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-syms-azure | 4.12.14-16.194.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 4.12.14-10.197.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_59 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0519 · May 22, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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-476 · NULL Pointer DereferenceCVSS 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)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.