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-2022-49761btrfs: always report error in run_one_delayed_ref()

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed refs for the abort transaction, run_one_delayed_ref() will just cleanup the refs and do nothing, thus no new error messages would be output.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 months 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-2022-49761, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.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.20% · top 90% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
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 79787eaab46121d4713ed03c8fc63b9ec3eaec76 – < 18bd1c9c02e64a3567f90c83c2c8b855531c8098
    • affected 79787eaab46121d4713ed03c8fc63b9ec3eaec76 – < fdb4a70bb768d2a87890409597529ad81cb3de8a
    • affected 79787eaab46121d4713ed03c8fc63b9ec3eaec76 – < 853ffa1511b058c79a4c9bb1407b3b20ce311792
    • affected 79787eaab46121d4713ed03c8fc63b9ec3eaec76 – < 39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92
  • Linux · Linux

    • affected 3.4
    • unaffected < 3.4
    • unaffected 5.10.165 – ≤ 5.10.*
    • unaffected 5.15.90 – ≤ 5.15.*
    • unaffected 6.1.8 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .