title: Junos OS: SRX Series: Memory leak when querying Aggregated Ethernet (AE) interface statistics
description: On Juniper Networks SRX Series devices with link aggregation (lag) configured, executing any operation that fetches Aggregated Ethernet (AE) interface statistics, including but not limited to SNMP GET requests, causes a slow kernel memory leak. If all the available memory is consumed, the traffic will be impacted and a reboot might be required. The following log can be seen if this issue happens. /kernel: rt_pfe_veto: Memory over consumed. Op 1 err 12, rtsm_id 0:-1, msg type 72 /kernel: rt_pfe_veto: free kmem_map memory = (20770816) curproc = kmd An administrator can use the following CLI command to monitor the status of memory consumption (ifstat bucket): user@device > show system virtual-memory no-forwarding | match ifstat Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ifstat 2588977 162708K - 19633958 <<<< user@device > show system virtual-memory no-forwarding | match ifstat Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ifstat 3021629 189749K - 22914415 <<<< This issue affects Juniper Networks Junos OS on SRX Series: 17.1 versions 17.1R3 and above prior to 17.3R3-S11; 17.4 versions prior to 17.4R3-S5; 18.2 versions prior to 18.2R3-S7, 18.2R3-S8; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R2-S7, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R3-S1; 20.1 versions prior to 20.1R2, 20.1R3; 20.2 versions prior to 20.2R2-S2, 20.2R3; 20.3 versions prior to 20.3R1-S2, 20.3R2. This issue does not affect Juniper Networks Junos OS prior to 17.1R3.
problem types: CWE-400 Uncontrolled Resource Consumption
affected:
{
platforms: SRX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 17.1*, status: affected, version: 17.1R3, versionType: custom
lessThan: 17.3R3-S11, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R3-S5, status: affected, version: 17.4, versionType: custom
lessThan: 18.2R3-S7, 18.2R3-S8, status: affected, version: 18.2, versionType: custom
lessThan: 18.3R3-S4, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2-S7, 18.4R3-S6, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R3-S4, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S6, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R3-S1, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R3-S1, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R2, 20.1R3, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R2-S2, 20.2R3, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R1-S2, 20.3R2, status: affected, version: 20.3, versionType: custom
}
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 17.1R3, status: unaffected, version: unspecified, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 7.5
baseSeverity: HIGH
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
version: 3.1
]
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following software releases have been updated to resolve this specific issue: 17.3R3-S11, 17.4R3-S5, 18.2R3-S7, 18.2R3-S8, 18.3R3-S4, 18.4R2-S7, 18.4R3-S6, 19.1R3-S4, 19.2R1-S6, 19.3R3-S1, 19.4R3-S1, 20.1R2, 20.1R3, 20.2R2-S2, 20.2R3, 20.3R1-S2, 20.3R2, 20.4R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.