CVE-2024-26877: crypto: xilinx - call finalize with bh disabled
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.73% (FIRST EPSS); higher than 54.5% of all records.
- 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 03e6d4e948432a61b35783323b6ab2be071d2619, 23bc89fdce71124cd2126fc919c7076e7cb489cf, 8a01335aedc50a66d04dd39203c89f4bc8042596.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 03e6d4e948432a61b35783323b6ab2be071d2619, 23bc89fdce71124cd2126fc919c7076e7cb489cf, 8a01335aedc50a66d04dd39203c89f4bc8042596 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: crypto: xilinx - call finalize with bh disabled When calling crypto_finalize_request, BH should be disabled to avoid triggering the following calltrace: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 74 at crypto/crypto_engine.c:58 crypto_finalize_request+0xa0/0x118 Modules linked in: cryptodev(O) CPU: 2 PID: 74 Comm: firmware:zynqmp Tainted: G O 6.8.0-rc1-yocto-standard #323 Hardware name: ZynqMP ZCU102 Rev1.0 (DT) pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : crypto_finalize_request+0xa0/0x118 lr : crypto_finalize_request+0x104/0x118 sp : ffffffc085353ce0 x29: ffffffc085353ce0 x28: 0000000000000000 x27: ffffff8808ea8688 x26: ffffffc081715038 x25: 0000000000000000 x24: ffffff880100db00 x23: ffffff880100da80 x22: 0000000000000000 x21: 0000000000000000 x20: ffffff8805b14000 x19: ffffff880100da80 x18: 0000000000010450 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000003 x13: 0000000000000000 x12: ffffff880100dad0 x11: 0000000000000000 x10: ffffffc0832dcd08 x9 : ffffffc0812416d8 x8 : 00000000000001f4 x7 : ffffffc0830d2830 x6 : 0000000000000001 x5 : ffffffc082091000 x4 : ffffffc082091658 x3 : 0000000000000000 x2 : ffffffc7f9653000 x1 : 0000000000000000 x0 : ffffff8802d20000 Call trace: crypto_finalize_request+0xa0/0x118 crypto_finalize_aead_request+0x18/0x30 zynqmp_handle_aes_req+0xcc/0x388 crypto_pump_work+0x168/0x2d8 kthread_worker_fn+0xfc/0x3a0 kthread+0x118/0x138 ret_from_fork+0x10/0x20 irq event stamp: 40 hardirqs last enabled at (39): [<ffffffc0812416f8>] _raw_spin_unlock_irqrestore+0x70/0xb0 hardirqs last disabled at (40): [<ffffffc08122d208>] el1_dbg+0x28/0x90 softirqs last enabled at (36): [<ffffffc080017dec>] kernel_neon_begin+0x8c/0xf0 softirqs last disabled at (34): [<ffffffc080017dc0>] kernel_neon_begin+0x60/0xf0 ---[ end trace 0000000000000000 ]---
- Published
- Apr 17, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- —
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.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 9.8
- 4.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel5.11 and later · before 5.15.153
- linux linux kernel5.16 and later · before 6.1.83
- linux linux kernel5.7 and later · before 5.10.214
- linux linux kernel6.7 and later · before 6.7.11
- linux linux kernel6.8 and later · before 6.8.2
- linux linux kernel6.2 and later · before 6.6.23
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.7affected
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before 8a01335aedc50a66d04dd39203c89f4bc8042596affected · git
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before 03e6d4e948432a61b35783323b6ab2be071d2619affected · git
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before a71f66bd5f7b9b35a8aaa49e29565eca66299399affected · git
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before 23bc89fdce71124cd2126fc919c7076e7cb489cfaffected · git
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before 9db89b1fb85557892e6681724b367287de5f9f20affected · git
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before dbf291d8ffffb70f48286176a15c6c54f0bb0743affected · git
- 4d96f7d48131fefe30d7c1d1e2a23ef37164dbf5 and later · before a853450bf4c752e664abab0b2fad395b7ad7701caffected · git
- before 5.7not affected · semver
- 5.10.214 and later · up to and including 5.10.*not 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:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.7.12-1 | 6.7.12-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-2024-26875Apr 17, 2024 · media: pvrusb2: fix uaf in pvr2_context_set_notify25Monitor
- ← EarlierCVE-2024-26876Apr 17, 2024 · drm/bridge: adv7511: fix crash on irq during probe22Monitor
- Later →CVE-2024-26878Apr 17, 2024 · quota: Fix potential NULL pointer dereference18Monitor
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 | 03e6d4e948432a61b35783323b6ab2be071d2619 | Vendor (CNA) |
| Linux Linux | 23bc89fdce71124cd2126fc919c7076e7cb489cf | Vendor (CNA) |
| Linux Linux | 8a01335aedc50a66d04dd39203c89f4bc8042596 | Vendor (CNA) |
| Linux Linux | 9db89b1fb85557892e6681724b367287de5f9f20 | Vendor (CNA) |
| Linux Linux | a71f66bd5f7b9b35a8aaa49e29565eca66299399 | Vendor (CNA) |
| Linux Linux | a853450bf4c752e664abab0b2fad395b7ad7701c | Vendor (CNA) |
| Linux Linux | dbf291d8ffffb70f48286176a15c6c54f0bb0743 | Vendor (CNA) |
| debian:linux | 6.1.85-1 · Debian:12 | 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.
No nightly-computed relations.
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)
—
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 (8 more)Show less
- git.kernel.org/stable/c/23bc89fdce71124cd2126fc919c7076e7cb489cf
- git.kernel.org/stable/c/8a01335aedc50a66d04dd39203c89f4bc8042596
- git.kernel.org/stable/c/9db89b1fb85557892e6681724b367287de5f9f20
- git.kernel.org/stable/c/a71f66bd5f7b9b35a8aaa49e29565eca66299399
- git.kernel.org/stable/c/a853450bf4c752e664abab0b2fad395b7ad7701c
- git.kernel.org/stable/c/dbf291d8ffffb70f48286176a15c6c54f0bb0743
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.