LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49960: drm/i915: fix null pointer dereference

In the Linux kernel, the following vulnerability has been resolved: drm/i915: fix null pointer dereference Asus chromebook CX550 crashes during boot on v5.17-rc1 kernel. The root cause is null pointer defeference of bi_next in tgl_get_bw_info() in drivers/gpu/drm/i915/display/intel_bw.c. BUG: kernel NULL pointer dereference, address: 000000000000002e PGD 0 P4D 0 Oops: 0002 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 1 Comm: swapper/0 Tainted: G U 5.17.0-rc1 Hardware name: Google Delbin/Delbin, BIOS Google_Delbin.13672.156.3 05/14/2021 RIP: 0010:tgl_get_bw_info+0x2de/0x510 ... [ 2.554467] Call Trace: [ 2.554467] <TASK> [ 2.554467] intel_bw_init_hw+0x14a/0x434 [ 2.554467] ? _printk+0x59/0x73 [ 2.554467] ? _dev_err+0x77/0x91 [ 2.554467] i915_driver_hw_probe+0x329/0x33e [ 2.554467] i915_driver_probe+0x4c8/0x638 [ 2.554467] i915_pci_probe+0xf8/0x14e [ 2.554467] ? _raw_spin_unlock_irqrestore+0x12/0x2c [ 2.554467] pci_device_probe+0xaa/0x142 [ 2.554467] really_probe+0x13f/0x2f4 [ 2.554467] __driver_probe_device+0x9e/0xd3 [ 2.554467] driver_probe_device+0x24/0x7c [ 2.554467] __driver_attach+0xba/0xcf [ 2.554467] ? driver_attach+0x1f/0x1f [ 2.554467] bus_for_each_dev+0x8c/0xc0 [ 2.554467] bus_add_driver+0x11b/0x1f7 [ 2.554467] driver_register+0x60/0xea [ 2.554467] ? mipi_dsi_bus_init+0x16/0x16 [ 2.554467] i915_init+0x2c/0xb9 [ 2.554467] ? mipi_dsi_bus_init+0x16/0x16 [ 2.554467] do_one_initcall+0x12e/0x2b3 [ 2.554467] do_initcall_level+0xd6/0xf3 [ 2.554467] do_initcalls+0x4e/0x79 [ 2.554467] kernel_init_freeable+0xed/0x14d [ 2.554467] ? rest_init+0xc1/0xc1 [ 2.554467] kernel_init+0x1a/0x120 [ 2.554467] ret_from_fork+0x1f/0x30 [ 2.554467] </TASK> ... Kernel panic - not syncing: Fatal exception (cherry picked from commit c247cd03898c4c43c3bce6d4014730403bc13032)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash certain systems during boot when the Intel i915 graphics driver initializes. The public record describes an Asus Chromebook CX550 on a 5.17 release-candidate kernel reaching a fatal kernel panic. Business impact is availability: affected devices may fail to boot until a fixed kernel is used.

Executive priority

Handle this as a stability and availability issue. It is not evidenced as actively exploited, but affected endpoints may be unable to boot. Patch through normal kernel maintenance, with faster action for fleets using Intel i915 graphics or affected Chromebook-class hardware.

Technical view

CVE-2022-49960 is a NULL pointer dereference of bi_next in tgl_get_bw_info() within drivers/gpu/drm/i915/display/intel_bw.c. The crash occurs during i915 hardware probing in early boot and can lead to kernel panic. The source references upstream/stable kernel commits resolving the defect, but provides no CVSS, CWE, or exploitability detail.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with Intel i915 graphics paths that exercise this bandwidth initialization logic. The only concrete impacted hardware named is Asus Chromebook CX550 / Google Delbin on Linux 5.17-rc1. Broader exposure should be verified against vendor kernel backports and the referenced commits.

Exploitation context

No active exploitation is reported in the supplied sources, and the CVE is not marked KEV. The evidence describes a boot-time crash rather than a remote attack path. Public details are insufficient to claim practical attacker exploitation, privilege impact, or network exposure.

Researcher notes

The record lacks CVSS, CWE, exploitability analysis, and complete product-version mapping. The affected-version data should be treated cautiously and reconciled with kernel git history and distribution backports. The strongest technical signal is the named NULL dereference and call trace in i915 initialization.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes for CVE-2022-49960.
  • Prioritize devices with Intel i915 graphics and affected kernel builds.
  • Avoid affected release-candidate kernels on impacted hardware.
  • Use vendor-supported kernels rather than ad hoc local patches.

Validation and detection

  • Inventory Linux kernel versions across Intel i915-equipped systems.
  • Compare deployed kernel changelogs against the referenced fix commits.
  • Review boot logs for tgl_get_bw_info or i915 kernel panic traces.
  • Test reboot on representative affected hardware after updating.
  • Confirm vendor advisory status for packaged kernel fixes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2022-49960 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc64a9a7c05beb2b71b7496d873654f88e1a08593, c64a9a7c05beb2b71b7496d873654f88e1a08593unaffected
LinuxLinux5.17, 0, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.