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-47505aio: fix use-after-free due to missing POLLFREE handling

Description

In the Linux kernel, the following vulnerability has been resolved: aio: fix use-after-free due to missing POLLFREE handling signalfd_poll() and binder_poll() are special in that they use a waitqueue whose lifetime is the current task, rather than the struct file as is normally the case. This is okay for blocking polls, since a blocking poll occurs within one task; however, non-blocking polls require another solution. This solution is for the queue to be cleared before it is freed, by sending a POLLFREE notification to all waiters. Unfortunately, only eventpoll handles POLLFREE. A second type of non-blocking poll, aio poll, was added in kernel v4.18, and it doesn't handle POLLFREE. This allows a use-after-free to occur if a signalfd or binder fd is polled with aio poll, and the waitqueue gets freed. Fix this by making aio poll handle POLLFREE. A patch by Ramji Jiyani <[email protected]> (https://lore.kernel.org/r/[email protected]) tried to do this by making aio_poll_wake() always complete the request inline if POLLFREE is seen. However, that solution had two bugs. First, it introduced a deadlock, as it unconditionally locked the aio context while holding the waitqueue lock, which inverts the normal locking order. Second, it didn't consider that POLLFREE notifications are missed while the request has been temporarily de-queued. The second problem was solved by my previous patch. This patch then properly fixes the use-after-free by handling POLLFREE in a deadlock-free way. It does this by taking advantage of the fact that freeing of the waitqueue is RCU-delayed, similar to what eventpoll does.

Timeline

  1. ID reserved

    By Linux

  2. · 2 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-47505, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (18 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: High 7.8.

Affected products

  • Linux · Linux

    • affected 2c14fa838cbefc23cf1c73ca167ed85b274b2913 – < 321fba81ec034f88aea4898993c1bf15605c023f
    • affected 2c14fa838cbefc23cf1c73ca167ed85b274b2913 – < 4105e6a128e8a98455dfc9e6dbb2ab0c33c4497f
    • affected 2c14fa838cbefc23cf1c73ca167ed85b274b2913 – < 47ffefd88abfffe8a040bcc1dd0554d4ea6f7689
    • affected 2c14fa838cbefc23cf1c73ca167ed85b274b2913 – < 60d311f9e6381d779d7d53371f87285698ecee24
    • affected 2c14fa838cbefc23cf1c73ca167ed85b274b2913 – < 50252e4b5e989ce64555c7aef7516bdefc2fea72
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 4.19.221 – ≤ 4.19.*
    • unaffected 5.4.165 – ≤ 5.4.*
    • unaffected 5.10.85 – ≤ 5.10.*
    • unaffected 5.15.8 – ≤ 5.15.*
    • unaffected 5.16 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .