crypto: tegra - Add missing CRYPTO_ALG_ASYNC
In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The tegra crypto driver failed to set the CRYPTO_ALG_ASYNC on its asynchronous algorithms, causing the crypto API to select them for users that request only synchronous algorithms. This causes crashes (at least). Fix this by adding the flag like what the other drivers do. Also remove the unnecessary CRYPTO_ALG_TYPE_* flags, since those just get ignored and overridden by the registration function anyway.
- Published
- May 1, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.6% · 47th percentile
- CWE
- CWE-617
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| 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 kernel6.10 and later · before 6.12.81
- linux linux kernel6.13 and later · before 6.18.22
- linux linux kernel6.19 and later · before 6.19.12
- linux linux kernel7.0
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
- 6.10affected
- 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before bdbf027a4504b4a86740de6beb6d18a957331839affected · git
- 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before 3aea268b6d5cde3b087df9eeecc3bc620aa09513affected · git
- 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before 429d05565eb19ee545d8a8395991372adbe4daf3affected · git
- 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before 4b56770d345524fc2acc143a2b85539cf7d74bc1affected · git
- before 6.10not affected · semver
- 6.12.81 and later · up to and including 6.12.*not affected · semver
- 6.18.22 and later · up to and including 6.18.*not affected · semver
- 6.19.12 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.12-1 | 6.19.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 3aea268b6d5cde3b087df9eeecc3bc620aa09513 | Vendor (CNA) |
| Linux Linux | 429d05565eb19ee545d8a8395991372adbe4daf3 | Vendor (CNA) |
| Linux Linux | 4b56770d345524fc2acc143a2b85539cf7d74bc1 | Vendor (CNA) |
| Linux Linux | bdbf027a4504b4a86740de6beb6d18a957331839 | Vendor (CNA) |
| Debian:linux | 6.12.85-1 · Debian:13 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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-2026-5295254 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2026-4611727 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
- CVE-2026-3139828 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2025-39803228 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2026-5295454 days apartlibceph: handle rbtree insertion error in decode_choose_args()30Monitor
- CVE-2026-6380679 days apartKVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned()28Monitor
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
- Anyone who can reach it over the internet 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/3aea268b6d5cde3b087df9eeecc3bc620aa09513
- git.kernel.org/stable/c/429d05565eb19ee545d8a8395991372adbe4daf3
- git.kernel.org/stable/c/4b56770d345524fc2acc143a2b85539cf7d74bc1
- git.kernel.org/stable/c/bdbf027a4504b4a86740de6beb6d18a957331839
Vendor advisories and official records. Exploit/PoC links are deliberately left out.