Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-47185tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc

Description

In the Linux kernel, the following vulnerability has been resolved: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-47185, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium4.4CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1Medium4.4CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.4.

Affected products

  • Linux · Linux

    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < 0380f643f3a7a61b0845cdc738959c2ad5735d61
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < b1ffc16ec05ae40d82b6e373322d62e9d6b54fbc
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < 4c1623651a0936ee197859824cdae6ebbd04d3ed
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < 4f300f47dbcf9c3d4b2ea76c8554c8f360400725
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < d491c84df5c469dd9621863b6a770b3428137063
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < 77e9fed33056f2a88eba9dd4d2d5412f0c7d1f41
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < 5c34486f04700f1ba04907231dce0cc2705c2d7d
    • affected 81de916f19cf5f1437c0b9ed817364f0f7c81961 – < 3968ddcf05fb4b9409cd1859feb06a5b0550a1c1
  • Linux · Linux

    • affected 3.0
    • unaffected < 3.0
    • unaffected 4.4.293 – ≤ 4.4.*
    • unaffected 4.9.291 – ≤ 4.9.*
    • unaffected 4.14.256 – ≤ 4.14.*
    • unaffected 4.19.218 – ≤ 4.19.*
    • unaffected 5.4.162 – ≤ 5.4.*
    • unaffected 5.10.82 – ≤ 5.10.*
    • unaffected 5.15.5 – ≤ 5.15.*
    • unaffected 5.16 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-47185 badge
[![CVE-2021-47185](https://cveledger.app/badge/CVE-2021-47185.svg)](https://cveledger.app/cve/CVE-2021-47185)

Record last updated .