LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50036: drm/sun4i: dsi: Prevent underflow when computing packet sizes

In the Linux kernel, the following vulnerability has been resolved: drm/sun4i: dsi: Prevent underflow when computing packet sizes Currently, the packet overhead is subtracted using unsigned arithmetic. With a short sync pulse, this could underflow and wrap around to near the maximal u16 value. Fix this by using signed subtraction. The call to max() will correctly handle any negative numbers that are produced. Apply the same fix to the other timings, even though those subtractions are less likely to underflow.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50036 is a Linux kernel bug in the sun4i DSI display driver. A short display timing value can make packet-size arithmetic underflow. The business impact is unclear from the sources because no CVSS score, CWE, crash impact, or privilege requirement is provided.

Executive priority

Set priority after confirming whether affected display-driver code exists in deployed products. For ordinary servers, urgency is likely low, but embedded Linux devices using this hardware path should be reviewed during the next kernel maintenance cycle.

Technical view

The flaw is in drm/sun4i DSI packet-size calculations. Packet overhead was subtracted using unsigned arithmetic, so short sync pulse or timing values could wrap near a maximum u16 value. Kernel stable commits fix this by using signed subtraction and max() handling.

Likely exposure

Exposure appears limited to Linux systems with affected kernels that include and use the drm/sun4i DSI driver, commonly embedded or ARM display deployments. The provided version data is incomplete and partly ambiguous, so confirm exposure against downstream kernel packages and vendor advisories.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. It also does not provide exploitability details, required privileges, attack vector, or observed abuse. Treat this as a kernel reliability or local device-risk issue until vendor guidance clarifies impact.

Researcher notes

Evidence supports a specific upstream kernel arithmetic fix, but not severity, exploitability, or real-world impact. The affected-version list in the bundle is not enough to determine all vulnerable downstream packages. Do not infer remote exploitability from this record.

Mitigation direction

  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Check distribution or device-vendor advisories for backported kernel packages.
  • Prioritize systems using Allwinner sun4i DSI display hardware or drivers.
  • Track kernel package provenance where vendor kernels diverge from upstream stable.
  • Avoid direct wrangler-style assumptions: follow vendor kernel guidance only.

Validation and detection

  • Inventory kernels and identify devices loading or building the sun4i DSI driver.
  • Compare deployed kernel versions with vendor advisories and referenced stable commits.
  • Confirm patched source uses signed subtraction in DSI packet-size timing calculations.
  • Review kernel update status on embedded images and appliance firmware.
  • Document systems not using this driver as lower-priority exposure.
Prepared
Confidence
medium
Sources
6

Public sources used

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-50036 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
5Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux133add5b5ad42b7bb5fcd59d681aef6475d08600, 133add5b5ad42b7bb5fcd59d681aef6475d08600, 133add5b5ad42b7bb5fcd59d681aef6475d08600, 133add5b5ad42b7bb5fcd59d681aef6475d08600unaffected
LinuxLinux4.18, 0, 5.10.138, 5.15.63, 5.19.4, 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.