{
  "cveId": "CVE-2022-49810",
  "url": "https://patchblox.com/security/cve/CVE-2022-49810",
  "summary": "CVE-2022-49810 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49810, released May 1, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "netfs: Fix missing xas_retry() calls in xarray iteration",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  netfs: Fix missing xas_retry() calls in xarray iteration  netfslib has a number of places in which it performs iteration of an xarray whilst being under the RCU read lock.  It *should* call xas_retry() as the first thing inside of the loop and do \u0022continue\u0022 if it returns true in case the xarray walker passed out a special value indicating that the walk needs to be redone from the root[*].  Fix this by adding the missing retry checks.  [*] I wonder if this should be done inside xas_find(), xas_next_node() and     suchlike, but I\u0027m told that\u0027s not an simple change to effect.  This can cause an oops like that below.  Note the faulting address - this is an internal value (|0x2) returned from xarray.  BUG: kernel NULL pointer dereference, address: 0000000000000402 ... RIP: 0010:netfs_rreq_unlock\u002B0xef/0x380 [netfs] ... Call Trace:  netfs_rreq_assess\u002B0xa6/0x240 [netfs]  netfs_readpage\u002B0x173/0x3b0 [netfs]  ? init_wait_var_entry\u002B0x50/0x50  filemap_read_page\u002B0x33/0xf0  filemap_get_pages\u002B0x2f2/0x3f0  filemap_read\u002B0xaa/0x320  ? do_filp_open\u002B0xb2/0x150  ? rmqueue\u002B0x3be/0xe10  ceph_read_iter\u002B0x1fe/0x680 [ceph]  ? new_sync_read\u002B0x115/0x1a0  new_sync_read\u002B0x115/0x1a0  vfs_read\u002B0xf3/0x180  ksys_read\u002B0x5f/0xe0  do_syscall_64\u002B0x38/0x90  entry_SYSCALL_64_after_hwframe\u002B0x44/0xae  Changes: ======== ver #2)  - Changed an unsigned int to a size_t to reduce the likelihood of an    overflow as per Willy\u0027s suggestion.  - Added an additional patch to fix the maths.",
  "published": "2025-05-01T15:16:04Z",
  "severity": "Moderate",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "cwe": "NULL Pointer Dereference",
  "epss": 0.0017,
  "epssPercentile": 0.06466,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-49810",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.10-1",
      "fix": "DEBIAN-CVE-2022-49810",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49810",
      "released": "2025-05-01T15:16:04Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.10-1",
      "fix": "DEBIAN-CVE-2022-49810",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49810",
      "released": "2025-05-01T15:16:04Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.10-1",
      "fix": "DEBIAN-CVE-2022-49810",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49810",
      "released": "2025-05-01T15:16:04Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}