Security readout for executives and security teams
Plain-English summary
CVE-2022-49456 is a Linux kernel bonding driver flaw involving missing RCU protection when timestamping information is queried. The record does not state a concrete business impact, CVSS score, or active exploitation, so urgency depends on whether exposed Linux systems use affected kernel builds and bonding.
Executive priority
Treat as a targeted kernel maintenance issue, not an emergency from the provided evidence. Prioritize patch planning for bonded Linux infrastructure, especially production network hosts, while tracking vendor advisories for package-specific status.
Technical view
The flaw is in bond_ethtool_get_ts_info(). It can be reached through setsockopt without an existing RCU read lock, which syzbot reported. The fix adds rcu_read_lock protection and takes a reference on the underlying real_dev before use.
Likely exposure
Exposure is most likely on Linux systems running affected 5.17 or 5.18-era kernels with network bonding enabled. The source bundle lists Linux as affected and references stable kernel fixes, but does not map every distribution package version.
Exploitation context
The bundle provides a kernel stack trace from syzbot and states the path can be reached via setsockopt. It does not cite public exploitation, weaponized proof-of-concept activity, or CISA KEV listing.
Researcher notes
Evidence is limited to the CVE record, stable kernel commits, and the syzbot-derived trace. No CVSS, CWE, affected distro matrix, exploitability assessment, or impact class is provided in the bundle.
Mitigation direction
- Apply vendor-supported Linux kernel updates containing the referenced stable fixes.
- Check distribution advisories for the exact fixed kernel package version.
- Prioritize bonded-network hosts if affected kernel versions are present.
- Use vendor guidance if backport status is unclear.
Validation and detection
- Inventory Linux kernel versions across servers and appliances.
- Identify hosts using the Linux bonding driver.
- Compare installed kernels with vendor fixed-version advisories.
- Confirm updated kernels include the referenced stable commits.
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-49456 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/1b66a533c47d29b38af8e05fbb53b609a5ba3a4eCVE reference, Linux
- https://git.kernel.org/stable/c/85eed460681da71b359ed906bce4d800081db854CVE reference, Linux
- https://git.kernel.org/stable/c/9b80ccda233fa6c59de411bf889cc4d0e028f2c7CVE 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.