Security readout for executives and security teams
Plain-English summary
This is a Linux kernel issue in the Intel MAX 10 BMC security FPGA driver. The fix corrects cleanup when device probing fails, preventing resource leaks. The sources do not provide CVSS, impact detail, or exploitation evidence, so urgency depends on affected kernel and hardware presence.
Executive priority
Track this as a targeted kernel maintenance item, not an emergency, unless exposed FPGA management systems are business-critical. Absence of CVSS and exploitation evidence lowers confidence in urgency, but kernel resource-leak fixes should still enter normal patch governance.
Technical view
The kernel fix is in fpga: m10bmc-sec and addresses improper probe error rollback. A failed probe could leave leaked resources. Public metadata lists affected Linux kernel versions around 6.0 through 6.2 and stable fixes, but provides no CWE, CVSS, or detailed security impact.
Likely exposure
Likely limited to systems running affected Linux kernels with the m10bmc-sec FPGA security driver or related hardware path enabled. Generic Linux systems without this driver or hardware are less likely exposed, but confirm through inventory.
Exploitation context
No active exploitation is reported in the provided sources, and KEV is false. The public description is a cleanup and rollback leak fix, not a documented remote attack path. Exploitability cannot be determined from the provided metadata.
Researcher notes
Evidence is sparse. The CVE description only states that probe error rollback was fixed to avoid leaks. No CWE, CVSS vector, exploit preconditions, privilege boundary, or user-triggerable path is provided in the source bundle.
Mitigation direction
- Review Linux vendor guidance for CVE-2022-49745 before operational changes.
- Upgrade to a kernel release containing the referenced stable fixes.
- Prioritize systems with Intel MAX 10 BMC security FPGA functionality.
- Use standard kernel update testing for hardware-dependent driver changes.
Validation and detection
- Inventory Linux kernel versions against the affected range in the CVE record.
- Check whether the m10bmc-sec driver is built, loaded, or used.
- Confirm the running kernel includes one of the referenced stable commits.
- Document systems where relevant FPGA hardware is absent or disabled.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-49745 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/74cff472d3d66db13b5ef64f40dfa42383f71ff7CVE reference, Linux
- https://git.kernel.org/stable/c/60ce26d10e5850f33cc76fce52f5377045e75a15CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.