GHSA-7R67-4HF5-JFM4

Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

clocksource/drivers/timer-sun4i: Advertise a real minimum delta

sun4i_clkevt_next_event() compensates for the timer stop/start synchronization delay by programming evt - TIMER_SYNC_TICKS into the hardware interval register. The clockevent device currently advertises TIMER_SYNC_TICKS as min_delta_ticks, so the clockevents core is allowed to call set_next_event() with evt == TIMER_SYNC_TICKS.

That programs a zero-tick interval. With oneshot/highres/nohz timer operation this can leave the next event stuck, which was observed as a boot hang on Allwinner D1 after the clockevents core started reusing forced minimum-delta events.

Advertise one extra tick instead, so the smallest event accepted by the core still programs at least one hardware tick after the synchronization compensation.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-93219"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-24T16:17:17Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclocksource/drivers/timer-sun4i: Advertise a real minimum delta\n\nsun4i_clkevt_next_event() compensates for the timer stop/start\nsynchronization delay by programming evt - TIMER_SYNC_TICKS into the\nhardware interval register. The clockevent device currently advertises\nTIMER_SYNC_TICKS as min_delta_ticks, so the clockevents core is allowed\nto call set_next_event() with evt == TIMER_SYNC_TICKS.\n\nThat programs a zero-tick interval. With oneshot/highres/nohz timer\noperation this can leave the next event stuck, which was observed as a\nboot hang on Allwinner D1 after the clockevents core started reusing\nforced minimum-delta events.\n\nAdvertise one extra tick instead, so the smallest event accepted by the\ncore still programs at least one hardware tick after the synchronization\ncompensation.",
  "id": "GHSA-7r67-4hf5-jfm4",
  "modified": "2026-09-24T18:31:23Z",
  "published": "2026-09-24T18:31:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93219"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0cc4b14d7401d50e53a01f1554147ee075ee6943"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/151eb52f8712017c8f7b00bb2305e8916cb9e3dc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/53a3bc024b8e5d284468cce84957cded5f859f98"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/753a220084dfc4d737f2ab9eaddc9a01a397edd7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bf38be01d43c4e4ca903aff7236d8486a950a252"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d21808328225ab8cee46885bf9a0dffcefbe630e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f0efafcdf6eec1f3361bfd8c811420198f55c8bb"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.

Loading…

Loading…

Loading…

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.


Loading…