GHSA-854R-XW42-GJ8X
Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-18 18:32In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Apply the fine-grained UNDEFs without FEAT_FGT
FGUs don't actually require hardware support, so don't gate fgt trap config insertion on FGT. This is the only action required to allow FGUs always, as kvm_calculate_traps() already computes the FGU bits with or without FEAT_FGT.
This also fixes a spurious WARN when a TLBI OS is run on a guest in vEL1 without FEAT_TLBIOS on non FEAT_FGT hardware. In this configuration the course-grained HCR_EL2.TTLBOS trap reaches the handler handle_tlbi_el1(), which expects an EL1 TLBI only from vEL2. With FGUs enabled the UNDEF will be injected without needing the specific handler.
[oliver: Take Wei-Lin's suggested changelog]
{
"affected": [],
"aliases": [
"CVE-2026-98713"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:24Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Apply the fine-grained UNDEFs without FEAT_FGT\n\nFGUs don\u0027t actually require hardware support, so don\u0027t gate fgt trap\nconfig insertion on FGT. This is the only action required to allow FGUs\nalways, as kvm_calculate_traps() already computes the FGU bits with or\nwithout FEAT_FGT.\n\nThis also fixes a spurious WARN when a TLBI OS is run on a guest in vEL1\nwithout FEAT_TLBIOS on non FEAT_FGT hardware. In this configuration the\ncourse-grained HCR_EL2.TTLBOS trap reaches the handler handle_tlbi_el1(),\nwhich expects an EL1 TLBI only from vEL2. With FGUs enabled the UNDEF\nwill be injected without needing the specific handler.\n\n[oliver: Take Wei-Lin\u0027s suggested changelog]",
"id": "GHSA-854r-xw42-gj8x",
"modified": "2026-10-18T18:32:00Z",
"published": "2026-10-18T18:32:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98713"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1113374a17d7f7d16b02ee0bbd9b1e7a60cbb087"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2f4a15c52a552c5244ec27f4ca8bda855594f918"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4bdd2b3a708c1feb701cb8b62feb8ad2fd77bb07"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/af3300b3a6bace925a496f3520e171c07b999c72"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.