{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54137 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54137 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-54137 and fix it if it is affected.\n\nWhat it is: CVE-2023-54137 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-54137 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-54137/ (Markdown: https://insights.sbomify.com/CVE-2023-54137/index.md)","id":"CVE-2023-54137","markdown":"https://insights.sbomify.com/CVE-2023-54137/index.md","name":"CVE-2023-54137","record":{"aliases":["BELL-CVE-2023-54137","DEBIAN-CVE-2023-54137","GHSA-78pw-r9wg-6p38","UBUNTU-CVE-2023-54137"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Local attackers can read uninitialized kernel memory via VFIO ioctl, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvfio/type1: fix cap_migration information leak\n\nFix an information leak where an uninitialized hole in struct\nvfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.\n\nThe definition of struct vfio_iommu_type1_info_cap_migration contains a hole as\nshown in this pahole(1) output:\n\n  struct vfio_iommu_type1_info_cap_migration {\n          struct vfio_info_cap_header header;              /*     0     8 */\n          __u32                      flags;                /*     8     4 */\n\n          /* XXX 4 bytes hole, try to pack */\n\n          __u64                      pgsize_bitmap;        /*    16     8 */\n          __u64                      max_dirty_bitmap_size; /*    24     8 */\n\n          /* size: 32, cachelines: 1, members: 4 */\n          /* sum members: 28, holes: 1, sum holes: 4 */\n          /* last cacheline: 32 bytes */\n  };\n\nThe cap_mig variable is filled in without initializing the hole:\n\n  static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,\n                         struct vfio_info_cap *caps)\n  {\n      struct vfio_iommu_type1_info_cap_migration cap_mig;\n\n      cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;\n      cap_mig.header.version = 1;\n\n      cap_mig.flags = 0;\n      /* support minimum pgsize */\n      cap_mig.pgsize_bitmap = (size_t)1 \u003c\u003c __ffs(iommu-\u003epgsize_bitmap);\n      cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;\n\n      return vfio_info_add_capability(caps, \u0026cap_mig.header, sizeof(cap_mig));\n  }\n\nThe structure is then copied to a temporary location on the heap. At this point\nit's already too late and ioctl(VFIO_IOMMU_GET_INFO) copies it to userspace\nlater:\n\n  int vfio_info_add_capability(struct vfio_info_cap *caps,\n                   struct vfio_info_cap_header *cap, size_t size)\n  {\n      struct vfio_info_cap_header *header;\n\n      header = vfio_info_cap_add(caps, size, cap-\u003eid, cap-\u003eversion);\n      if (IS_ERR(header))\n          return PTR_ERR(header);\n\n      memcpy(header + 1, cap + 1, size - sizeof(*header));\n\n      return 0;\n  }\n\nThis issue was found by code inspection.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vfio/type1: fix cap_migration information leak","id":"CVE-2023-54137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"drm/msm: fix NULL-deref on irq uninstall","id":"CVE-2023-54138"},"packages":[],"prev":{"headline":"serial: sprd: Fix DMA buffer leak issue","id":"CVE-2023-54136"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"Local attackers can read uninitialized kernel memory via VFIO ioctl, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2023-54137/"}